Looking into durable objects more today - they need to be binded to a worker which is the same probl

Looking into durable objects more today - they need to be binded to a worker which is the same problem I have with d1.

DDean Looking into durable objects more today - they need to be binded to a worker whi...

Sort of? You bind a DO namespace to your Worker once, but from that namespace, you pass an ID and get as many DOs as you want

Hello, I’m Allie!•5/18/25, 4:15 PM

One Namespace -> Many “Databases”

gruntlord6•5/19/25, 12:28 AM

yup, you can have a lot of individual objects in a single namespace

gruntlord6•5/19/25, 12:28 AM

for example, an object for every customer

gruntlord6•5/19/25, 12:29 AM

where as with D1 you need a binding for every db

planet•5/19/25, 1:52 AM

Does a primary get replicated to multiple replicas, or just a single replica per region?

e.g. does a WNAM primary gets replicated to a single ENAM location, or multiple ENAM locations?

Pplanet Does a primary get replicated to multiple replicas, or just a single replica per...

Chaika•5/19/25, 2:02 AM

currently just one replica per region, including the primary region

Rripes Bumping this. Any pointers on importing an existing sqlite db that already has a...

Max (@rozenmd)•5/19/25, 8:18 AM

https://developers.cloudflare.com/d1/best-practices/import-export-data/#known-limitations

Disciple of Caoximeihao•5/19/25, 9:16 AM

Is there a way to export the database but still have it read and write normally in production?

Disciple of Caoximeihao•5/19/25, 9:16 AM

Is there a way to export the database but still have it read and write normally in production?

xeon06•5/19/25, 3:43 PM

Is there anyone working on a D1 client for workers with built-in retry, to try and circumvent these issues? https://github.com/cloudflare/cloudflare-docs/issues/18485

xeon06•5/19/25, 3:56 PM

I suppose it isn't that simple to enforce idempotency

.ul0gic•5/19/25, 6:46 PM

anyone here familiar or have experience in getting local D1 instances to maintain persistence during local development by chance?

.ul0gic•5/19/25, 7:35 PM

Fixing D1 Local Persistence with Wrangler Pages Dev

Issue

Local D1 persistence with

wrangler pages dev

wrangler pages dev

may not work as expected, even when

preview_database_id

preview_database_id

is set in

wrangler.toml

wrangler.toml

and --persist-to--persist-to is used in the

dev

dev

script. Runtime operations (e.g., API calls creating new data) might connect to a new, blank D1 instance instead of the schema-initialized, persisted one. This leads to "no such table" errors and data loss between development server restarts.

message.txt2.15KB

.ul0gic•5/19/25, 7:37 PM

sorry if that breaks the rules....ive seen a few people ask about this and have this same issue. took multiple days and finally figured it out. hope it helps someone else here struggling with this.

DDean i get DO's exist, but i built the platform around D1 with dynamic bindings comin...

lambrospetrou•5/20/25, 7:39 AM

D1 dynamic bindings are not coming in the short-term, and still undecided for long-term. If you want to programmatically create thousands of databases, SQLite Durable Objects are already available and they are the exact same SQLite components under the hood.

Llambrospetrou D1 dynamic bindings are not coming in the short-term, and still undecided for lo...

DeanOP•5/20/25, 7:44 AM

It’s a shame that really wasn’t communicated at the start. I’ll have to rewrite everything which is a shame.

DDean It’s a shame that really wasn’t communicated at the start. I’ll have to rewrite ...

lambrospetrou•5/20/25, 9:00 AM

At the start, SQLite DOs didn't exist

Ashish Rawat•5/20/25, 9:42 AM

Durable object is too much boilerplate.

planet•5/20/25, 2:18 PM

meh it only took less than a week to learn how to use SQLite in DO and refactor code

planet•5/20/25, 2:18 PM

you get input gates & (in my testing) much better latencies & less reads/writes because you dont need to index a user id

Ashish Rawat•5/20/25, 2:51 PM

problem is you can't query across multiple database for getting list of users, do joins and so on. So you've to use D1 for that with different concept. Cloudflare database (D1, DO) is broken. D1 has different limitation while DO has different. So basically to make everything work, you need to use both D1, DO and Queues. So instead of this, I better off go with managed postgres.

AAshish Rawat problem is you can't query across multiple database for getting list of users, d...

lambrospetrou•5/20/25, 3:47 PM

So you've to use D1 for that with different concept. Cloudflare database (D1, DO) is broken. D1 has different limitation while DO has different

I wonder why you say this. Actually, D1 has exactly the same limitations as a single Durable Object, and even more since your worker code is remotely from the actual storage and you don't have things like transactions across queries interleaved with JS code, whereas in the DO case your code runs next to the storage and is fast. Resource limits wise, a D1 database IS a single Durable Object, so zero differences.

I assume your different viewpoint is if you design your DO architecture using per-resource/per-tenant DO vs a single D1 database, but then you are not comparing the same thing since managing multiple D1 databases in the same way would be much more complicated.

planet•5/20/25, 8:35 PM

Much less of a problem and more of a design consideration.

Personally I use D1 as a lightweight directory DBs that handles background cleanups/etc (via CRON) and login lookups. emails/sso metadata matches get logged into their SQLite in DO DB.

You also have Alarms which is part of Durable Objects (so you don't necessarily need Queues/Workflows)
You can also set up basic rate limiting in memory using

this

this

in each new constructor instance

planet•5/20/25, 8:37 PM

Now I do wish my R2 bucket had spawned in the same DC as my DO... praying for finer grained location hints one day

workerBee•5/20/25, 9:13 PM

Is it possible to debug these platform errors?

D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.

D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.

.... Or just accept and move on?

Llambrospetrou D1 dynamic bindings are not coming in the short-term, and still undecided for lo...

ac•5/21/25, 12:43 AM

This is definitely different from the messaging that I've heard from other Cloudflare folks recently, I was definitely hoping for dynamic bindings for D1 as well. It's a bit disappointing how unclear this all is.

SQLite in DO's is a nice idea, but it's fairly unusable right now when you can't actually view DO instances and cannot view what is in the databases....

Aac This is definitely different from the messaging that I've heard from other Cloud...

1984 Ford Laser•5/21/25, 5:50 AM

There are absolutely ways to view the instances and view what's in the databases. Unsure where that idea comes from exactly

Aac This is definitely different from the messaging that I've heard from other Cloud...

lambrospetrou•5/21/25, 6:15 AM

This is definitely different from the messaging that I've heard from other Cloudflare folks recently

I have been in this channel for 9 months now and we never gave an ETA for dynamic bindings. It was (and still is) one of the future possible features. But, I don't want folks to start designing their new applications now depending on a feature that does not yet exist and is not going to land within say the next quarter. That's my viewpoint.

SQLite in DO's is a nice idea, but it's fairly unusable right now when you can't actually view DO instances and cannot view what is in the databases....

You cannot (yet) view them natively in the Cloudflare dashboard but there are several open source solutions to inspect your Durable Objects. For example, you could use something like https://github.com/outerbase/browsable-durable-object
I agree that DOs don't (yet) have some of the niceties of D1 like import/export but you get the flexibility of creating as many as you want much easier than with D1. So, it's about tradeoffs and what you need right this moment.

Aac This is definitely different from the messaging that I've heard from other Cloud...

DeanOP•5/21/25, 7:01 AM

Yeah it truly sucks. I have workarounds for it and looking at using durable objects but think I’ll end up just using another database provider that’ll allow me to do everything d1 does but have a database for each user,

Ashish Rawat•5/21/25, 8:02 AM

Well that proves the point, neither D1 nor DO solves the basic problems completely. Why would we should use 10 different things when all can be done with postgres and postgres doesn't have 10 GB limitation.
Also this is not just the problem with DO or D1, even workers doesn't have many limitations, basically all the development products of cloudflare are just WIP and not ready for production usage completely.

AAshish Rawat Well that proves the point, neither D1 nor DO solves the basic problems complete...

lambrospetrou•5/21/25, 8:50 AM

If Postgres solves your needs, then using Workers + Hyperdrive is a perfectly fine combination. There is no need to shoehorn your architecture into the D1/DO model.

Himanshu•5/21/25, 11:30 AM

I'm unable to use D1 outside of the Workers environment. I tried in Node.js, but I'm having trouble accessing the bindings. Any solution for this?

SuperHelpflare•5/21/25, 11:31 AM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

11984 Ford Laser There are absolutely ways to view the instances and view what's in the databases...

ac•5/21/25, 11:41 AM

The only solution I'm aware of is using a REST API and sending raw queries through that, would love to know if there is a better/more native way

Aac The only solution I'm aware of is using a REST API and sending raw queries throu...

gruntlord6•5/21/25, 12:19 PM

you can also use a worker as a proxy

DDean Yeah it truly sucks. I have workarounds for it and looking at using durable obje...

gruntlord6•5/21/25, 12:20 PM

honestly its not that big of a limit when you consider all the benifits of a durable object for each user

gruntlord6•5/21/25, 12:21 PM

things like alarms are huge

Aac The only solution I'm aware of is using a REST API and sending raw queries throu...

lambrospetrou•5/21/25, 12:30 PM

See my link to outerbase's projects that exposes the Studio UI they have for each of your DOs. At some point we should be adding that natively into the dashboard, but until then you can use the library version.

Llambrospetrou > This is definitely different from the messaging that I've heard from other Clo...

João Castro•5/21/25, 5:23 PM

Dynamic bindings and transactions were two things that we saw being mentioned as coming :soontm: multiple times in the past, even in official blog posts

João Castro•5/21/25, 5:23 PM

Honestly today I don't really care anymore because DOs with SQLite solve those problems so that is great

João Castro•5/21/25, 5:24 PM

Just that D1 feels like something that currently sits in a very weird spot

João Castro•5/21/25, 5:42 PM

And I have the impression that we might see something like the Functions/Pages and Workers convergence happening with D1 and DOs in the future

Original message was deleted

lambrospetrou•5/22/25, 8:00 AM

That error doesn't seem to be a D1 error. Are you using any ORM library? If yes, how are you using it?

blackfish•5/22/25, 8:55 AM

Prisma + SQLite/D1: Error when creating record with null values

Hey guys I'm encountering a PrismaClientUnknownRequestErrorPrismaClientUnknownRequestError when trying to create a record with null values using Prisma with D1 database SQLite. The error suggests a JSON parsing failure, but the input data appears valid.

Error Message:

PrismaClientUnknownRequestError: Invalid `prisma.table_name.create()` invocation:
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(SqliteError { extended_code: 1, message: Some("D1_ERROR: Failed to parse body as JSON, got: ") }), transient: false })

PrismaClientUnknownRequestError: Invalid `prisma.table_name.create()` invocation:
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(SqliteError { extended_code: 1, message: Some("D1_ERROR: Failed to parse body as JSON, got: ") }), transient: false })

Reproduction Steps:

Schema (Prisma): ```prismamodel TableName {id Int @id @default(autoincrement())owner Stringamount IntamountUsd Float? @map("amount_usd")// ... other fields with nullable ones marked as ?@@map("table_name")

}

2. Schema (D1 DB):

2. Schema (D1 DB):

sql
CREATE TABLE table_name (
id INTEGER PRIMARY KEY AUTOINCREMENT,
owner TEXT NOT NULL,
amount INTEGER NOT NULL,
amount_usd REAL,
... other fields
)

3. Attempted Query:

3. Attempted Query:

typescript
await prisma.tableName.create({
data: {
amount: 100000,
amountUsd: null, // This nullable field seems to trigger the issue
owner: "xyz_onwer",
// ... other fields
}
});

``

Record should be created with

``

Record should be created with

NULL for nullable fields (like for nullable fields (like amountUsd

).

**Issue:**  
Fails with JSON parsing error, even though:  
- Schema correctly marks field as optional (

).

**Issue:**  
Fails with JSON parsing error, even though:  
- Schema correctly marks field as optional (

Float?

)  
- SQLite table allows NULL (

)  
- SQLite table allows NULL (

amount_usd REAL

)  

Here one thing to note (which is kind of weird) is that, once I try to insert

)  

Here one thing to note (which is kind of weird) is that, once I try to insert

null` all the subseuent values into the field will result in same error, like 1, 1.343 etc. And after a while, it wil work again without fail.

Also sometimes the null value also gets accepted.
I am not clear what I am doing wrong here.
If anyone could help me on this, it would be very helpful.

Original message was deleted

Isaac McFadyen•5/22/25, 12:01 PM

How are you defining a "connection is not possible"? Can you show the actual code that you are throwing the error with?

jonast•5/22/25, 2:40 PM

When using cloudflare D1 and drizzle, how can I do data migrations (in addition to schema migrations)

Specifically, I have a table like this

export const users = sqliteTable("users", {
id: text("id")
.primaryKey()
.$defaultFn(() => prefixID("user")),
googleId: text("google_id").notNull().unique().default(""),
email: text("email").notNull().unique(),
name: text("name").notNull(),
avatarUrl: text("avatar_url"),
createdAt: integer("created_at", { mode: "timestamp" }).$defaultFn(() => new Date())
});

I want to now break out the googleId into a separate table that maps external Id (google ID) to internal user ID. But I want to migrate all values

What are my options?

Just stick that data migration into a SQL file?

Looking into durable objects more today - they need to be binded to a worker which is the same probl

Issue

Similar Threads

Similar Threads

Issue

Similar Threads