●Change8

Migrating to Drizzle ORM v1.0.0-rc.4

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

Released: 6/27/2026

2
Breaking Changes
2
Migration Steps
34
Affected Symbols

⚠️ Check Your Code

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

ViewSubquerySQLPreparedQuerypgsqlitedb.$countsqlite entities' genericsDrizzleQueryErrordb.batch()CockroachArrayBuilderdb.selectbun-sql/pgsqlite RQBv2dialect.buildSelectionorderSelectedFieldsPGMySQLsql.paramPlaceholderdrizzle-orm/effect-schemaBufferblob columnsql operatorgeneratedByDefaultAsIdentitydb.insert(table).select(...)@tursodatabase/database@tursodatabase/database-wasmSQLiteSyncDialectSQLiteAsyncDialectmigrateSyncmigrateAsyncEffectCacheShape@effect/sql-pg

Breaking Changes

●Issue #1

Removed RQBv1 from `sqlite`, removed RQBv1 `TSchema`, `TFullSchema` arguments from `sqlite` entities' generics. Users relying on RQBv1 generics for SQLite entities must update their code.

●Issue #2

Removed `mapResult` method from `PreparedQuery` interface, removed `mapResult`, `mapBatchResult` from `pg` and `sqlite` raw queries. Code using these methods must be updated to use alternative result mapping strategies.

Migration Steps

  1. 1
    Update generics for SQLite entities by removing `TSchema` and `TFullSchema` arguments related to RQBv1.
  2. 2
    Replace usage of `.mapResult` or `.mapBatchResult` on `PreparedQuery`, `pg`, or `sqlite` raw queries with alternative mapping logic.

Release Summary

This release introduces significant architectural changes, particularly splitting SQLite and MySQL into async/effect variants, and overhauling result mapping APIs. Numerous fixes address issues across PostgreSQL, SQLite, and MySQL dialects, alongside improved SQL operator typing.

Need More Details?

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

View Full Changelog