Upgrade Prisma from 5.20.0 to 6.2.0 #11888
Conversation
|
Thanks for getting started on this. Very exciting! Would love to be able to upgrade to the latest Prisma version |
See https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 Especially 6.2 brings exciting new features, most importantly `json` and `enum` fields for SQLite, but also the `omit`-feature (the antagonist to `include`), the `updateManyAndReturn` batch function, or the support for auto-generated cuid2 and ulid values. For a quick overview of the new features, refer to the release notes: - https://github.com/prisma/prisma/releases/tag/6.2.0 - https://github.com/prisma/prisma/releases/tag/6.1.0 - https://github.com/prisma/prisma/releases/tag/6.0.0 This is, of course, a candidate for the next major version of RedwoodJS. The migration process looks smooth, we should never- theless start on a writeup to highlight the new features and the most important migration steps.
A feature that was introduced with Prisma v6.0 See prisma/prisma-engines#5009 and prisma/prisma#25722
|
This was a whole lot simpler than expected :) Also |
Philzen
force-pushed
the
chore/update-prisma-to-v6.2
branch
from
9bef774 to
829d89c
Compare
|
Looking at the breaking changes for Prisma v6 this one stood out to me
I'm worried/concerned about how that might affect the Prisma <-> GQL type mapping. Might be a non-issue. But I'd like us to look into at least, before we merge this PR. And we should also think about any codemods we could write for any of the breaking changes they've listed. |
See https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6
Especially 6.2 brings exciting new features, most importantly
jsonandenumfields for SQLite, but also theomit-feature (the antagonist toinclude), theupdateManyAndReturnbatch function, or the support for auto-generated cuid2 and ulid values.For a quick overview of the new features and improvements since 5.20, refer to the release notes:
This is, of course, a candidate for the next major version of RedwoodJS. The migration process looks smooth, we should never- theless start on a writeup to highlight the new features and the most important migration steps.