Change8

Migrating to Drizzle ORM v1.0.0-rc.1

Version v1.0.0-rc.1 introduces 2 breaking changes. This guide details how to update your code.

Released: 4/30/2026

2
Breaking Changes
3
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

drizzledrizzle-orm/pg-coredrizzle-orm/dialect-coredrizzle-orm/effect-postgresdrizzle-orm/netlify-db

Breaking Changes

Issue #1

The legacy casing API (e.g., `const db = drizzle({..., casing: "camel" })`) has been removed and replaced with a new API where casing control is applied at the table, view, or schema level using `snakeCase` or `camelCase` imports from `drizzle-orm/pg-core` or `drizzle-orm/dialect-core`. To fix, update table definitions to use the new casing constructors (e.g., `d.snakeCase.table(...)`).

Issue #2

Removed RQB v1 `._query` support for postgres dialect. Users relying on this internal API must migrate to RQB v2 or newer methods.

Migration Steps

  1. 1
    If using the legacy casing API (`casing: "camel"` in drizzle instantiation), update table definitions to use the new casing API, e.g., `d.snakeCase.table("users", ...)`.
  2. 2
    If using RQB v1 `._query` for postgres, migrate to RQB v2 or newer query methods.
  3. 3
    Moved pg array utilities (`makePgArray`, `parsePgArray`) from `drizzle-orm/pg-core/utils[/array]` to `drizzle-orm/pg-core/array`. Update imports accordingly.

Release Summary

Version 1.0.0-rc.1 introduces major performance enhancements via JIT mappers and a new codec system, alongside native Effect v4 support and a new Netlify driver. This release also contains breaking changes by removing the legacy casing API and RQB v1 postgres support.

Need More Details?

View the full release notes and all changes for Drizzle ORM v1.0.0-rc.1.

View Full Changelog