warningBreaking change
Drizzle ORM v1.0.0-rc.1: casing API and RQBv1 removed
- Announced
- 4 May 2026
- Effective
- no date announced
- Version
- 1.0.0-rc.1
- Source
- the vendor’s own page · last checked 29 Sept 2026
What breaks
This release breaks existing code in two ways for postgres users.
- The old casing API, set via
drizzle({ casing: "camel" })on the db instance, no longer works as before. db._query(RQBv1) has been removed entirely for postgres.- Code importing
makePgArray/parsePgArrayfromdrizzle-orm/pg-core/utilsordrizzle-orm/pg-core/utils/arraywill break, since those moved todrizzle-orm/pg-core/array. - Code relying on effect-schema/effect-postgres with Effect v3 will break, since those packages switched to Effect v4 beta.
What to do
Update code to match the new APIs before upgrading.
- Move casing control from the db instance to the table/view/schema level, using
snakeCase/camelCaseimported fromdrizzle-orm/dialect-core. - Replace any use of
db._query(RQBv1) on postgres with RQBv2 or the new mappers. - Update imports of
makePgArray/parsePgArraytodrizzle-orm/pg-core/array. - Upgrade effect-schema and effect-postgres usage to Effect v4 beta.
What the vendor said
Drizzle ORM's v1.0.0-rc.1 release reworks internals with a new codec system for the postgres dialect, adds opt-in JIT mappers for faster row mapping, and adds native Effect v4 support. It also ships two breaking changes: a reworked casing API and the removal of RQBv1 (db._query) for postgres.