Smooth upgrade path from Prisma 1 to Prisma 2.0
See original GitHub issueWe’re planning to have a smooth upgrade path for existing Prisma 1 users.
The plan is to have:
- extensive documentation on the upgrade process
- Upgrading a REST API
- Upgrading a GraphQL API based on
nexus-prisma
- Upgrading a GraphQL API based on
prisma-binding
to Nexus - Upgrading a GraphQL API based on
prisma-binding
to SDL-first
- additional tooling that help transforming a Prisma 1 project into a Prisma 2 project
Issue Analytics
- State:
- Created 3 years ago
- Reactions:30
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Smooth upgrade path from Prisma 1 to Prisma 2.0 · Issue #1937
We're planning to have a smooth upgrade path for existing Prisma 1 users. The plan is to have: extensive documentation on the upgrade...
Read more >How to upgrade from Prisma 1 to Prisma version 2.x and later
Upgrading the Prisma layer: No matter what your Prisma 1 setup looks like, you should always start your upgrade process by following this...
Read more >Upgrade from Prisma 1 to Prisma 2
In this section. How to upgrade · Schema incompatibilities · Upgrading the Prisma layer · Old to new Nexus ...
Read more >Upgrading the Prisma layer to Prisma 2 | PostgreSQL
This page explains the first step of your upgrade process: Taking your Prisma 1 configuration and upgrading it to Prisma 2. Concretely, you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey everyone, thanks a lot for staying patient 🙏 I want to share another quick update on the state of the upgrade path to Prisma 2.0.
We’ve just published a new docs page that has a lot of helpful information regarding the upgrade process.
Most importantly, it points out all relevant schema incompatibilies and different workarounds that can be applied. For most of the workarounds, you’ll actually be able to use the Prisma schema upgrade CLI tool that we’re also working on.
As next steps, we will start working on more detailed migration guides for upgrading GraphQL APIs with
prisma-binding
andnexus
. (Side-note for @LeonardoGentile, Prisma 2.0 doesn’t supportprisma-binding
any more. Alternatively you can use a plain SDL-first approach withgraphql-tools
or use GraphQL Nexus, this will be explained in the upcoming migration guides).Hey folks 🙌 here comes another update regarding the upgrade process to Prisma 2.0!
First version of an upgrade guide for
prisma-binding
We have started working on more upgrade guides, a first one that explains how to upgrade a
prisma-binding
app to Prisma 2.0 and Nexus is now available as a first version. While the guide already contains a lot of helpful information, it is still _work in progress (that’s why it’s not yet available in the main Prisma docs, but only as a preview URL).I would love to get feedback for the
prisma-binding
guide and learn more about how helpful it is to you! If you’re currently running aprisma-binding
app and consider upgrading, please get in touch via email for ping me on Slack (I’m@nikolasburk
there).A new repository for dedicated upgrade feedback
I’ve also created a new repository that should serve as a central place to collect questions and issues about your upgrade process.
If you’re currently running Prisma 1 and are planning to upgrade soon, please open an issue there and share some more details about your upgrade scenario.
If you have any other questions or issues, feel free to create a new GitHub issue to raise these.