Drizzle ORM Transaction Error with D1 Database

V

Vinodh•8/6/25, 9:14 AM

Issue Description

Getting a transaction error when using Drizzle ORM's .transaction() method with Cloudflare D1 database.

Getting a transaction error when using Drizzle ORM's .transaction() method with Cloudflare D1 database.

Getting a transaction error when using Drizzle ORM's .transaction() method with Cloudflare D1 database.

Getting a transaction error when using Drizzle ORM's .transaction() method with Cloudflare D1 database.

Error Message:

Error: To execute a transaction, please use the state.storage.transaction() or state.storage.transactionSync() APIs instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.

Error: To execute a transaction, please use the state.storage.transaction() or state.storage.transactionSync() APIs instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.

Error: To execute a transaction, please use the state.storage.transaction() or state.storage.transactionSync() APIs instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.

Error: To execute a transaction, please use the state.storage.transaction() or state.storage.transactionSync() APIs instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.

Is there a workaround or recommended pattern for atomic operations in D1?

Any plans to support D1 transactions in Drizzle?

Anyone else encountered this? What's the recommended approach for multi-table operations in D1 with Drizzle?

V

Vinodh•8/6/25, 9:16 AM

using .transaction()

// This code fails in D1
const result = await this.db.transaction(async (tx) => {
  const updatedUser = await tx.update(user)
    .set(userUpdateData)
    .where(eq(user.id, input.id))
    .returning()
    .get();

  if (!updatedUser) {
    throw new Error("User not found");
  }

  // Additional operations...
  return updatedUser;
});

// This code fails in D1
const result = await this.db.transaction(async (tx) => {
  const updatedUser = await tx.update(user)
    .set(userUpdateData)
    .where(eq(user.id, input.id))
    .returning()
    .get();

  if (!updatedUser) {
    throw new Error("User not found");
  }

  // Additional operations...
  return updatedUser;
});

// This code fails in D1
const result = await this.db.transaction(async (tx) => {
  const updatedUser = await tx.update(user)
    .set(userUpdateData)
    .where(eq(user.id, input.id))
    .returning()
    .get();

  if (!updatedUser) {
    throw new Error("User not found");
  }

  // Additional operations...
  return updatedUser;
});

// This code fails in D1
const result = await this.db.transaction(async (tx) => {
  const updatedUser = await tx.update(user)
    .set(userUpdateData)
    .where(eq(user.id, input.id))
    .returning()
    .get();

  if (!updatedUser) {
    throw new Error("User not found");
  }

  // Additional operations...
  return updatedUser;
});

V

Vinodh•8/6/25, 9:18 AM

Got it! Thanks for clarifying

V

Vinodh•8/6/25, 9:18 AM

Creating a Drizzle issue since this seems like something the ORM should handle natively for D1 compatibility.

V

Vinodh•8/6/25, 9:18 AM

For now, I'll remove transactions and handle the operations sequentially until Drizzle adds proper D1 transaction support

C

cloudkite•8/6/25, 9:21 AM

@Vinodh D1 doesnt support transactions see https://github.com/cloudflare/workers-sdk/issues/2733

GitHub

🚀 Feature Request: D1 Transaction support · Issue #2733 · clou...

Describe the solution Has the procedures feature mentioned in this article been shipped? This feature does not seem to be available in the current version sdk, either locally or remotely. Is there ...

Original message was deleted

V

Vinodh•8/6/25, 9:23 AM

oh ho!

V

Vinodh•8/6/25, 9:25 AM

Ah, that explains a lot! This isn't actually a Drizzle issue

V

Vinodh•8/6/25, 9:25 AM

So for regular D1 usage (non-DO), there's simply no transaction support at all?

C

cloudkite•8/6/25, 9:25 AM

you can use db.batch

C

cloudkite•8/6/25, 9:26 AM

but its a bit more limited in comparison to transactions so might not fit for certain use cases

C

cloudkite•8/6/25, 9:28 AM

https://developers.cloudflare.com/d1/worker-api/d1-database/#batch

Cloudflare Docs

D1 Database

To interact with your D1 database from your Worker, you need to access it through the environment bindings provided to the Worker (env).

V

Vinodh•8/6/25, 9:28 AM

Perfect! Thanks for pointing that out!

Batch operations will do a multiple statements executed together, but not true transactions ? no automatic rollback on errors?

C

cloudkite•8/6/25, 9:28 AM

its a transaction, but you can't refer to results from other calls

V

Vinodh•8/6/25, 9:29 AM

Got it! That makes perfect sense.

V

Vinodh•8/6/25, 9:29 AM

So db.batch() gives me all succeed or all fail

V

Vinodh•8/6/25, 9:29 AM

but can't use results from one statement in another

C

cloudkite•8/6/25, 9:30 AM

Batched statements are SQL transactions ↗. If a statement in the sequence fails, then an error is returned for that specific statement, and it aborts or rolls back the entire sequence.

Batched statements are SQL transactions ↗. If a statement in the sequence fails, then an error is returned for that specific statement, and it aborts or rolls back the entire sequence.

Batched statements are SQL transactions ↗. If a statement in the sequence fails, then an error is returned for that specific statement, and it aborts or rolls back the entire sequence.

Batched statements are SQL transactions ↗. If a statement in the sequence fails, then an error is returned for that specific statement, and it aborts or rolls back the entire sequence.

V

Vinodh•8/6/25, 9:31 AM

That's exactly what I needed to know.

V

Vinodh•8/6/25, 9:32 AM

Going with db.batch() instead of db.transaction().
Really appreciate the help sorting this out!

Drizzle ORM Transaction Error with D1 Database

Similar Threads

Similar Threads

Similar Threads