Prisma•8mo ago•

8 replies

Getting foreign key error even though foreign row exists

I have two tables connected by a foreign key constraint. My

foo

foo

foo

foo table has a

foo_uuid

foo_uuid

foo_uuid

foo_uuid column, and my

bar

bar

bar

bar table references it via a

foo_uuid

foo_uuid

foo_uuid

foo_uuid column. I am trying to call this method:

prismaClient.bar.create({
  data: {
    foo_uuid: 123,
    other_bar_field: "whatever"
  }
})

prismaClient.bar.create({
  data: {
    foo_uuid: 123,
    other_bar_field: "whatever"
  }
})

prismaClient.bar.create({
  data: {
    foo_uuid: 123,
    other_bar_field: "whatever"
  }
})

prismaClient.bar.create({
  data: {
    foo_uuid: 123,
    other_bar_field: "whatever"
  }
})

I have DBeaver open and can see that there is a row in the

foo

foo

foo

foo table with

foo_uuid = 123

foo_uuid = 123

foo_uuid = 123

foo_uuid = 123, but when I run the

create

create

create

create method I get an error: "Foreign key constraint violated". It has code

P2003

P2003

P2003

P2003 and says the error is on the

foo_uuid

foo_uuid

foo_uuid

foo_uuid foreign key constraint.

Thing is, not only does the

foo

foo

foo

foo exist, but I can also insert this row into

bar

bar

bar

bar using DBeaver without any errors. What's going on? Is there some additional argument that's needed for the

create

create

create

create call when a foreign key exists?