@prisma/adapter-planetscale
7.10.1 · 15 Oct 2026Apache-2.069.3k / weekRepositorynpmAtom feed
Upgrading @prisma/adapter-planetscale From 7.2.0 to 7.3.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- breaking7.3.0
5 other lines we could not sort, mostly version bumps
- 7.3.0
Fast and Small Query Compilers We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new
compilerBuildoption for the client generator block inschema.prismawith two options:fastandsmall. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, thefastmode is used, but this can be set by the user: - 7.3.0
Bypass the Query Compiler for Raw Queries Raw queries (
$executeRaw,$queryRaw) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead. - 7.3.0
Update MSSQL to v12.2.0 This community PR updates the
@prisma/adapter-mssqlto use MSSQL v12.2.0. Thanks Jay-Lokhande! - 7.3.0
Pin better-sqlite3 version to avoid SQLite bug An underlying bug in SQLite 3.51.0 has affected the
better-sqlite3adapter. We’ve bumped the version that powers@prisma/better-sqlite3and have pinned the version to prevent any unexpected issues. If you are using@prisma/better-sqlite3, please upgrade to v7.3.0. - 7.3.0
prisma-engines#5745: Cast BigInt to text in JSON aggregation When using
relationJoinswith BigInt fields in Prisma 7, JavaScript'sJSON.parseloses precision for integers larger thanNumber.MAX_SAFE_INTEGER(2^53 - 1). This happens because PostgreSQL'sJSONB_BUILD_OBJECTreturns BigInt values as JSON numbers, which JavaScript cannot represent precisely.