I am about to upgrade fro Prisma1 to Prisma2 and a...
# orm-help
b
I am about to upgrade fro Prisma1 to Prisma2 and am a little bit confused as to which client I should go with. I have been using
prisma-binding
in my backend along with
graphql-yoga
and would like to migrate to either
prisma-client
or
nexus
- which ever one takes the least time to upgrade to! Which of the two would people recommend?
j
These two do different things, and work best together :). However,
nexus
recently "retired" their graphql framework, and instead put all their focus on their
schema
instead. So one recommended stack you might see here is: •
apollo server
for the general graphql server (really is almost identical to
graphql-yoga
) •
nexus/schema
for the graphql schema generation (define resolver and graphql data-model in one). You will want to use the prisma plugin to get close functionality to
prisma-binding
•
prisma
for the database access (to be used in your resolvers as defined in
nexus/schema
b
Thanks for clarifying Jonathan, had anyone written a comprehensive guide for migrating something like this? Seems not do straight forward!
r
Hey @Ben Liger šŸ‘‹ I would suggest going through the migration guide we have here in the docs which show all the steps for a successful migration šŸ™‚
šŸ‘ 1
s
@Samrith Shankar ā¬†ļø Just a little more evidence that there is a breakdown in communication between v1 and v2.
s
breakdown
šŸ˜‚ 1
b
clicking the first link in the upgrade guide "Upgrading the Prisma layer" lead to a
404
untill i opened it in a new tab btw
Also experiencing these errors when running the introspect. It's on a database that I know for sure has data in it. Any ideas?