Skip to content
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

[legacy-framework] Feat: Add next-prisma-plugin #1374

Closed

Conversation

JoseRFelix
Copy link

Closes: #225

What are the changes and their implications?

Changes

Implications

Blitz server won't need to restart after schema change and CRUD generated.

Checklist

  • Tests added for changes
  • PR submitted to blitzjs.com for any user facing changes

@flybayer
Copy link
Member

Thanks @JoseRFelix! Initially I was hoping prisma could somehow fix the multi connection error that necessitated the globalThis.prisma code. However, it seems quite unlikely and we need to keep that code in.

However, currently the prisma plugin won't work with that code. So I've opened prisma-labs/next-prisma-plugin#20 to fix this and make them compatible.

So need to let this set for a bit to see what happens with that.

@flybayer
Copy link
Member

I'm going to close this for now. See #225 (comment)

@flybayer flybayer closed this Feb 22, 2021
@itsdillon itsdillon changed the title Feat: Add next-prisma-plugin [legacy-framework] Feat: Add next-prisma-plugin Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blitz needs to restart after schema change and CRUD generated
2 participants