Is there a migration guide for those that want to use their data from the Prisma Admin with Prisma 2?

Hey @cfree 👋 Are you using the demo Prisma server?

@Ryan I was.. I gave up on the migration, am back to trying to use the typescript-client with Prisma 1 but it's different from using prisma-bindings (which I can't use in a Netlify Function). How do I use the query contained in the

info

AST when the generated functions don't accept that parameter? I tried using

$fragment()

, but I'm missing a step - I need to somehow flatten the

info

AST and pass it to

$fragment

for everything to work again 😅

Hey @cfree 🙌 with Prisma 1, it's not possible to pass the

info

argument to Prisma client any more (that's indeed the main difference compared to

prisma-binding

). However, we are currently working on migration guides, e.g. from

prisma-binding

to Prisma 2.0 with

nexus

here: https://deploy-preview-356--prisma2.netlify.app/guides/upgrade-from-prisma-1/upgrading-prisma-binding-to-nexus/ I'd love to get some feedback for the content, would you be interested in taking a stab at this one?

@nikolasburk I know, that's why I'm trying to figure out a way to use the

info

AST with the

$fragment

function - I'm so close to being done with this project, this is 18 months in the making. I'm trying to launch this sucker and I don't really want to make radical changes to my API. Once this is launched, I'd be happy to look at upgrade paths again...

Ha I see, yeah I don't think this is possible at the moment (at least from the features you get with Prisma client 1.0). It might be possible to write such a lib yourself though, for example @Ahmed build a similar library for the Prisma 2.0 Client, maybe that can serve as inspiration: https://github.com/AhmedElywa/prisma-tools/tree/master/packages/select