Error: Database error: Foreign key constraint failed

Bug description

I have the following schema:

model User {
  id                String @id @default(uuid())
  ...
  address           Address? @relation(fields: [id], references:[entityId])
}

model Address {
  entityId    String @id
  city        String?
  line1       String?
  line2       String?
  postalCode  String?
  user        User?
}

I execute: npx prisma db push

I am using: Postgres

The error I get:

Error: Database error
Foreign key constraint failed: User_id_fkey
   0: sql_migration_connector::sql_database_step_applier::apply_migration
             at migration-engine/connectors/sql-migration-connector/src/sql_database_step_applier.rs:15
   1: migration_core::api::SchemaPush
             at migration-engine/core/src/api.rs:163

Am I missing something conceptually? The data model seems valid to me. I use the VS Code plugin to lint my schema and it’s not showing any errors.

How to reproduce

As seen above.

Expected behavior

The new data model to be pushed correctly to the database.

Prisma information

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

Version: "prisma": "^2.22.1",

Environment & setup

• OS: MacOS
• Database: PostgreSQL
• Node.js version: 12.14.0
• Prisma version: 2.22.1

prisma               : 2.22.1
@prisma/client       : 2.21.2
Current platform     : darwin
Query Engine         : query-engine 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 60cc71d884972ab4e897f0277c4b84383dddaf6c
Studio               : 0.379.0

[Lucaspaula6]

It happened with me. I was getting the same error when creating objects inside objects in a relation from one to many.

The issue has been causd by the hierarchaly minor object beeing created before the higher one.

The solution was to seed manually object by object.

Other cause to the error was the object being created with the id bond and the “father” had a different id.

I’ve used prisma.objectname.create with id inclused. One by one.

Hope it helped.

Obs.: I thought about make an logical sequence that allows the subsquent seed to happen only after previous. Didn’t implement anything like that. If somebody implemented this solution or have a better one, please let me know.

Obrigado. =) [e-mail]

[janpio]

So in your case @archcra it was caused by a mismatch between your SQL schema pointing the Foreign Key to one table, and the Prisma Schema relation pointing to another model?