-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to replace Knex with Prisma #276
Comments
Looks very interesting @isBatak, it seems that it supports pretty much everything covered by Knex. However, instead of replacing, I'd like to keep support for Knex, since it's already there. On the long run, if we add more support for packages like Knex or Prisma, we'd need to create a Have you used Prisma before? I'm not entirely familiar with it. |
Yeah, wrong title... it should be more like "Ability to replace Knex with Prisma". I like the To be honest I don't have a real experience with Prisma but it seems like a great solution for I agree that this is a long shot for now... |
Interesting. You might want to take a look at #282 then, since we're starting to include features to make Kurier compatible with serverless environments as well. The fact that Prisma works out-of-the-box with Next.js also makes me want to explore more how an integration would look like. |
I saw #282 and I'm really excited and can't wait to test it... is it included in 1.2.0-alpha1 version? |
Yes, you can try it out in |
This is just an idea, but it would be cool to support Prisma and implement PrismaProcessor.
https://www.prisma.io/
The text was updated successfully, but these errors were encountered: