search

prisma / p1-to-p2-upgrade-path-feedback

4 stars 1 forks source link

Migration v1 - NN #1

Open alan345 opened 4 years ago

alan345 commented 4 years ago

Your Prisma 1 stack

I am building a GraphQL API. Stack is in production for 1 year

I am running Prisma version prisma/1.34.10

I am accessing my Prisma server with: 'prisma-binding'

with ctx.db.query.(...) or with ctx.db.mutation.(...) or with prismaBinding.forwardTo

Are you currently using nexus-prisma?

I am using MySQL 5.7

My Prisma server is hosted on AWS EC2

My database is hosted on AWS RDS

My API server is hosted on AWS EC2

Is there anything else that's worth mentioning about your stack?

Nope

Your upgrade plans

What's your preferred upgrade strategy?

Do you want to use the new Nexus Framework when you upgrade?

Nope. I Think I will do it as a second step, after upgrading primsa2

Do you have any remaining questions or comments?

  1. Do you confirm that no changes will be done on the database? (In case I need to rollback the migration)
  2. Should I implement prisma-client in prisma v1 before the migration to v2? or should I do the migration to v2 first?
  3. Any ETA when the tool to upgrade the schema will be available?
  4. Should I keep ctx.db.query in my resolvers?

Quick recommendation, why no doing 1 video example?

Thanks guys! You did an amazing job!

nikolasburk commented 4 years ago

Hey @alan345 👋 thanks a lot for sharing this! I'd love to hear your thoughts about the new prisma-binding upgrade guide which you can find here.

It's still somewhat in progress but it should contain the most important information about the upgrade process. If you decide to give it a shot and use it for the upgrade, please let us know the issues and questions you ran into while following the guide.