Can get prisma dev to align with production
- The migration
- Drift detected: Your database schema is not in sync with your migration history.
The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.
It should be understood as the set of changes to get from the expected schema to the actual schema.
[] Changed the
[] Altered column
[] Altered column
[] Altered column
[] Changed the
[] Altered column
[] Altered column
[] Altered column
√ We need to reset the "public" schema at "aws-0-ap-southeast-2.pooler.supabase.com:5432"
Do you want to continue? All data will be lost. ... no
I've tried everything online, how do i get my dev to align with production.
0_init- Drift detected: Your database schema is not in sync with your migration history.
The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.
It should be understood as the set of changes to get from the expected schema to the actual schema.
[] Changed the
Receipt[] Altered column
totalAmountVatInclusive[] Altered column
totalAmountVatExclusive[] Altered column
vatAmount[] Changed the
ReceiptItem[] Altered column
price[] Altered column
quantity[] Altered column
taxRate√ We need to reset the "public" schema at "aws-0-ap-southeast-2.pooler.supabase.com:5432"
Do you want to continue? All data will be lost. ... no
I've tried everything online, how do i get my dev to align with production.
