Conflict on seeding production db

[simonszalai]

I'm getting a foreign key conflict issue that might be caused by the db cleanup function. Interestingly, it only happens in Github Actions. If I insert this data as a part of a migration:

-- Insert for Organization
INSERT INTO "Organization" ("name", "nameLower")
VALUES ('Platform Admin Organization', 'platform admin organization');

-- Step 1: Insert UserAccount
INSERT INTO "UserAccount" ("email", "firstName", "lastName", "nameLower", "picture", "kindeId", "roles", "suspended", "createdAt", "organizationId")
VALUES ('example@email.com', 'First', 'Last', 'first last', 'picture_url', 'kinde_id', '["role1", "role2"]', false, CURRENT_TIMESTAMP, 1);

-- Step 2: Insert UserSettings using the hardcoded userAccountId
INSERT INTO "UserSettings" ("schedulerStartHour", "schedulerEndHour", "schedulerBreakMinutes", "startOfWeek", "userAccountId")
VALUES (8, 17, 30, 'monday', 1);

-- Step 3: Update UserAccount with userSettingsId
-- Assuming the ID of the newly inserted UserSettings is also 1, or you fetch it if needed
UPDATE "UserAccount"
SET "userSettingsId" = 1
WHERE "id" = 1;

I'm getting these errors:

prisma:error Raw query failed. Code: `1811`. Message: `FOREIGN KEY constraint failed`
prisma:error Raw query failed. Code: `1811`. Message: `FOREIGN KEY constraint failed`
prisma:error Raw query failed. Code: `1811`. Message: `FOREIGN KEY constraint failed`
prisma:error Raw query failed. Code: `1811`. Message: `FOREIGN KEY constraint failed`

[kentcdodds]

I wonder if this is happening because the DB you have cached in your github action is missing these changes or something. Have you tried deleting the cache?