Michael Buller
01/28/2022, 9:37 PMnpx prisma migrate dev --create-only
Environment variables loaded from .env
Prisma schema loaded from libs\api\core\data-access\src\prisma\schema.prisma
Datasource "db" - SQL Server
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.
[+] Added tables
• stage_Providers
[*] Changed the ProviderSearch
table
[+] Added column geography
? We need to reset the database.
Do you want to continue? All data will be lost. » (y/N)
My table has geography String? @ignore on it, the geography type is not supported by prisma yet... so have to work around it somehow. How do I tell Prisma not to touch that column and move on? Also, this is a production database and people need to move data into it via different methods. Seen here, there is a stage table that was added. We need a way to ignore that table. Also, don't you think it is odd that your only option you present to the user when a "New" table is added is to DELETE all of the other data from the database? Even if this was development, and we have all of the Prisma seed methods in place, deletion all data doesn't seem like the first choice I would go with.