Jolg42
commented
2 years ago Hi @LawJolla, you are almost there I see! Let's get you to the final part 💯
So Prisma Migrate (v2 & v3) relies on a _prisma_migrations table to record which migrations were applied (with success or not).
Since you are coming from Prisma 1 with an existing database, it doesn't exist
When this table doesn't exist migrate dev will always ask for reset and is not safe to use against a production database.
You will need to baseline your production database, it will create that table and mark the baseline migration to be ignored.
I would recommend you to use pg_dump to create the baseline migration to get the perfect copy of your database schema.
Then try it out locally with prisma migrate dev (no need to baseline locally).
If your local env works, then you can go for base lining the production (or staging) database using prisma migrate resolve [....]
See more details in https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/baselining
LawJolla
janpio
Your Prisma 1 stack
What are you building with Prisma?
I am building ... multiple services, including GraphQL and REST, backed by a Prisma/Postgres instance.
Which version of Prisma 1 are you running?
I am running Prisma version ... 1.34
How do you access your Prisma server?
I am accessing my Prisma server with ... Prisma Client
Are you currently using
nexus-prisma(with Prisma 1)?How many Prisma services are you running on your production Prisma server?
2
Which database (incl. version) do you use?
I am using ... Postgres 10
Where is your Prisma server hosted?
My Prisma server is hosted on ... Fargate
Where is your database hosted?
My database is hosted on ... AWS
Where is your API server hosted?
My API server is hosted on ... Render
Your upgrade plans
What's your preferred upgrade strategy?
Do you want to use the new Nexus Framework when you upgrade?
Y
When do you want to upgrade?
Do you have any remaining questions or comments?
Thank you for everyone's hard work!
I need help syncing my schema.prisma with my migrated Prisma 1 db schema.
For background, I'm a solo developer with a massive Prisma 1 project. I've been working on this project since Prisma was GraphCool 2.0 so the amount of technical debt is enormous.
I spent at least 150 hours over the last several months migrating. I did the following..
Copied the Prisma 1 production schema for migration. Ran the prisma upgrade tool against my Prisma 1 datamodel. Made various SQL migrations manually. Changed Prisma Client 1 calls to Prisma Client 3. Upgraded Nexus (the bulk of my time)
What I'd like to do now it copy my current Prisma 1 schema, run the needed migrations, and cut the updated servers over to the new Prisma 3 client / migrated Prisma 1 schema.
The problem is I'm unable to sync my migration schema with schema.prisma.
Specifically, I can't even get an initial migration. I followed the directions here: https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project#update-the-development-environment
I do not have any migration folder or files. However, I get the following output. Any help is very appreciated!