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 was modified after it was applied.- 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 table[] Altered column
totalAmountVatInclusive (type changed)[] Altered column
totalAmountVatExclusive (type changed)[] Altered column
vatAmount (type changed)[] Changed the
ReceiptItem table[] Altered column
price (type changed)[] Altered column
quantity (type changed)[] Altered column
taxRate (type changed)√ 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.
