Prisma•2mo ago

Null constraint violation on the fields: (`ownerId`)

With the following schema when I try and create a new Project I get then Null constraint violation for field ownerId which doesn't exist anymore

model Project {
  id      String @id @unique @default(cuid(2))
  name    String
  rows    Row[]
}

model Row {
  rowId     String   @id @default(cuid(2))
  number    Int
  projectId String
  stitches  Stitch[]
  project   Project  @relation(fields: [projectId], references: [id])
}

model Stitch {
  id        String     @id @default(cuid(2))
  number    Int
  rowId     String
  completed Boolean    @default(false)
  row       Row        @relation(fields: [rowId], references: [rowId])
  type      StitchType
}

enum StitchType {
  Single
  Increase
}

model User {
  id            String         @id @unique @default(cuid(2))
  createdAt     DateTime       @default(now()) @map("created_at")
  updatedAt     DateTime?      @updatedAt @map("updated_at")
  email         String?        @unique
  givenName     String?
  familyName    String?
  emailVerified Boolean?       @map("email_verified") @default(false)
  archive       Boolean        @default(false)
  googleId      String?
  yahooId       String?
  // projects      Project[]
  session       Session[]
  verification  Verification[]

  @@unique([id, email])
  @@unique([email, givenName, familyName])
  @@index([id, email])
  @@map("users")
}

model Project {
  id      String @id @unique @default(cuid(2))
  name    String
  rows    Row[]
}

model Row {
  rowId     String   @id @default(cuid(2))
  number    Int
  projectId String
  stitches  Stitch[]
  project   Project  @relation(fields: [projectId], references: [id])
}

model Stitch {
  id        String     @id @default(cuid(2))
  number    Int
  rowId     String
  completed Boolean    @default(false)
  row       Row        @relation(fields: [rowId], references: [rowId])
  type      StitchType
}

enum StitchType {
  Single
  Increase
}

model User {
  id            String         @id @unique @default(cuid(2))
  createdAt     DateTime       @default(now()) @map("created_at")
  updatedAt     DateTime?      @updatedAt @map("updated_at")
  email         String?        @unique
  givenName     String?
  familyName    String?
  emailVerified Boolean?       @map("email_verified") @default(false)
  archive       Boolean        @default(false)
  googleId      String?
  yahooId       String?
  // projects      Project[]
  session       Session[]
  verification  Verification[]

  @@unique([id, email])
  @@unique([email, givenName, familyName])
  @@index([id, email])
  @@map("users")
}

3 Replies

Prisma AI Help•2mo ago

You've gone full bot mode! Let me fetch that AI answer for you ASAP. Based on the information in your schema and the error you're experiencing, it appears you're facing a null constraint violation for a field called ownerId that no longer exists in your schema. This issue is similar to the one described in Github Issue #26284, where removing a field from a schema can sometimes lead to constraint violations during migrations or operations. The error suggests that your database still has a constraint or column related to ownerId even though it's been removed from your Prisma schema. This commonly happens when: 1. You previously had a relation between Project and User (likely through an ownerId field) 2. You removed this relation from your schema (as evidenced by the commented out // projects Project[] in your User model) 3. But the database still has the column and/or constraint There are a few approaches to resolve this: 1. Check if there's a mismatch between your Prisma schema and the actual database schema. You might need to run a migration to properly remove the ownerId column. 2. If you're using migrations, you might need to create a new migration that explicitly drops the column or constraint. 3. In some cases, you might need to reset your database schema completely as described in this Prisma discussion: - Delete all migration files (rm -rf prisma/migrations) - Delete migration records from the database (DELETE FROM "_prisma_migrations";) - Create a new baseline migration - Apply the cleaned-up SQL script to the database If you're using prisma db push instead of migrations, try running it with the --force-reset flag to force a reset of the database schema to match your Prisma schema. Remember that these operations might result in data loss, so make sure to back up any important data before proceeding. 🤔 Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly. In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.

UncleOP•2mo ago

I completely deleted my database am still getting this error

Nurul•2mo ago

That's strange. When exactly do you get this error? I assume while you are doing a query? To confirm, you PrismaClient is in sync with the schema.prisma file, correct?

Gaming

Programming

Null constraint violation on the fields: (`ownerId`)

Did you find this page helpful?