It could also be related to prisma not importing t...
# orm-helpb
Biel Simon
03/21/2019, 5:01 AMIt could also be related to prisma not importing the data in the correct odrer? And maybe some foreign key constraints have to be removed and re-added back when data is in place?
Biel Simon
03/21/2019, 5:36 AMA portion of the log by the postgres instance:
Biel Simon
03/21/2019, 5:37 AM2019-03-21 052820.112 UTC [28043] ERROR: insert or update on table "_CompanyToInvoice" violates foreign key constraint "_CompanyToInvoice_A_fkey"
2019-03-21 052820.112 UTC [28043] DETAIL: Key (A)=(cjth8x5zd1y450a39jlmrxflp) is not present in table "Company".
2019-03-21 052820.112 UTC [28043] STATEMENT: insert into "default$staging"."_CompanyToInvoice" (
"A",
"B"
)
(
$1,
$2,
$3
)
2019-03-21 052820.140 UTC [28063] ERROR: insert or update on table "_LicenseKeyToRenewalType" violates foreign key constraint "_LicenseKeyToRenewalType_A_fkey"
2019-03-21 052820.140 UTC [28063] DETAIL: Key (A)=(cjth8wqym1ngd0a394iupwl5e) is not present in table "LicenseKey".
2019-03-21 052820.140 UTC [28063] STATEMENT: insert into "default$staging"."_LicenseKeyToRenewalType" (
"A",
"B"
)
(
$1,
$2,
$3
)
h
Harshit
03/21/2019, 3:48 PM@Biel Simon
Can you please provide us a reproduction of this issue?
If so, please open a github issue about this 🙏
b
Biel Simon
03/21/2019, 4:08 PMYes
Biel Simon
03/21/2019, 4:09 PM(We have discussed this more in a thread 4 messages above)
Biel Simon
03/21/2019, 4:09 PMBut I put here what I put on the github issue
Biel Simon
03/21/2019, 4:09 PMI was using the same exact prisma instance that operated on the same postgres instance.
The apparent reason it was not working is because the docker volume that contained the postgres data was full / not allowed to grow by docker. I fixed it by cleaning unused images and volumes. Maybe a guide on how to configure the docker volume appropriately to store arbitrary amounts of data would be helpful.
h
Harshit
03/21/2019, 4:14 PMThanks for the feedback