Well that proves the point, neither D1 nor DO solves the basic problems completely. Why would we sho

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

PrismaClientUnknownRequestError

PrismaClientUnknownRequestError

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?

Jjonast When using cloudflare D1 and drizzle, how can I do data migrations (in addition ...

CodingCoop | Co-Founder Nullshot•5/22/25, 2:57 PM

I usually stay in the migration file and what wrangler has versus trusting anything outside of that.

It works well.

verdverm.com•5/25/25, 11:18 PM

Did the concept of D1 Procedures ever get implemented? (https://blog.cloudflare.com/whats-new-with-d1/)

The Cloudflare Blog

D1: our quest to simplify databases

Get an inside look on the D1 experience today, what the team is currently working on and what’s coming up!

Vverdverm.com Did the concept of D1 Procedures ever get implemented? (https://blog.cloudflare....

Larry•5/26/25, 12:08 AM

I'm not sure if they ever intended differently but a version of that was implemented when they brought the SQLite storage engine to Durable Objects. My impression is that the success of DOs is the reason why features like D1 Procedures and Dynamic Binding have not been implemented.

gruntlord6•5/26/25, 1:59 AM

I think they more or less said DOs will support the same things as D1 at some point, but they each have some features that the other does not

gruntlord6•5/26/25, 1:59 AM

I could be remembering what they said wrong though

cosbgn•5/26/25, 12:42 PM

Hey id d1 down or something?

cosbgn•5/26/25, 12:42 PM

I keep getting :D1 DB exceeded its CPU time limit and was reset. [code: 7500] when trying to run a migration

cosbgn•5/26/25, 12:46 PM

I'm stuck - migration passed locally but d1 just runs out of cpu

aliendev•5/26/25, 8:21 PM

Hi, I've just discovered Outerbase Studio from the recent Acquisition announcement, it's great news to see it become part of CloudFlare. I was thinking about implementing it in a project I'm working on, but I found that the license is AGPL which prevents me from doing that without making my codebase public. Since the original cloud offering is now closed for new users and sunsetting soon, and seeing that the original repo is no longer active, would it be possible to make the license less prohibitive ?

Aaliendev Hi, I've just discovered Outerbase Studio from the recent Acquisition announceme...

lambrospetrou•5/27/25, 9:19 AM

I was thinking about implementing it in a project I'm working on

Do you mean using the Outerbase Studio with your D1 databases, or do you just want to use it in a completely different project unrelated to D1? Just clarifying since this the D1 channel.

aliendev•5/27/25, 11:36 AM

I want to make it part of my hosted dashboard, so that my users can access and edit their own DBs, which are all part of a single multi-tenant D1 database (and the project itself will be deployed using CF workers).
so to answer your question, my use case is for a different project, but related to D1 and fully part of the CF ecosystem.

Aaliendev I want to make it part of my hosted dashboard, so that my users can access and e...

lambrospetrou•5/27/25, 11:55 AM

I will ask the outerbase folks and let you know (or they will reply directly)

aliendev•5/27/25, 12:15 PM

thank you

Brayden•5/27/25, 2:56 PM

@aliendev At the moment there are no plans to change the license on the repositories, sorry...

BBrayden @aliendev At the moment there are no plans to change the license on the reposito...

aliendev•5/27/25, 3:11 PM

got it, no worries. thanks !

Paul Mihai•5/28/25, 2:23 PM

Hi everyone, I have a 3gb database with multiple keys (one line can be quite large - a few kb - but the blobs are not part of any keys), the maximum size is 10gb, but for some reason querying even this small DB is very slow (even simple queries take up to a minute). I use composite keys. Anybody else seeing this type of behavior? Noteworthy is the fact that this db experiences a lot of writes as it is a live stats marting table.

Spencer•5/28/25, 2:39 PM

hey, i need some help please, got an error D1 ERROR: Currently processing a long-running export, how to cancel this operation ? cause because of it my app stops working

SSpencer hey, i need some help please, got an error D1 ERROR: Currently processing a long...

lambrospetrou•5/28/25, 3:40 PM

If you are doing an export the whole DB is blocked until it uploads everything to R2. If you want to abort the export, then unfortunately you need to stop polling and wait a few seconds for it to stop.

PPaul Mihai Hi everyone, I have a 3gb database with multiple keys (one line can be quite lar...

lambrospetrou•5/28/25, 3:42 PM

What is the

.meta

.meta

information telling you about the duration of the query itself? 1 minute is very long either way and probably hints to other issues, commonly overloaded DB due to traffic or slow-ish consecutive queries.
Also, are all your queries slow, or just that specific one?

Paul Mihai•5/28/25, 3:42 PM

Writing seems to be perfectly fine, but querying especially on high writing load is suuuuper slow

Paul Mihai•5/28/25, 3:43 PM

we have a few million writes / day

PPaul Mihai Writing seems to be perfectly fine, but querying especially on high writing load...

lambrospetrou•5/28/25, 3:43 PM

Keep in mind that D1 is single threaded. Only one query executes at a time.

Paul Mihai•5/28/25, 3:43 PM

but just a few reads a day

Paul Mihai•5/28/25, 3:43 PM

so the problem may be the queue

Paul Mihai•5/28/25, 3:43 PM

because we have so many writes?

PPaul Mihai so the problem may be the queue

lambrospetrou•5/28/25, 3:44 PM

Yes, maybe. Check the

meta

meta

field of the responses for the duration listed. If that's small (a few milliseconds) then the issue is not the query itself. It can be either the volume of your load (number of requests and time each write query takes to finish) or some networking issue. The latency of the query is also available in the UI and through wrangler insights.

Paul Mihai•5/28/25, 3:45 PM

I'll do that! Thanks! Also I understood there is a "new" version of D1?

Paul Mihai•5/28/25, 3:46 PM

is that still a thing or were all migrated to the new backend?

Llambrospetrou If you are doing an export the whole DB is blocked until it uploads everything t...

Spencer•5/28/25, 3:46 PM

but i am not polling atm, it's just stuck, there is a way to cancel the process somehow ?

PPaul Mihai I'll do that! Thanks! Also I understood there is a "new" version of D1?

lambrospetrou•5/29/25, 10:30 AM

You probably mean a new version of Durable Objects, not D1. The SQLite based DOs are new-ish yes, but D1 was already built ontop of those. There is no new version of D1.

Zig•5/29/25, 6:23 PM

Does anyone have experience troubleshooting

D1_ERROR: Failed to parse body as JSON, got: Error: internal error;

D1_ERROR: Failed to parse body as JSON, got: Error: internal error;

D1_ERROR: database is locked: SQLITE_BUSY

D1_ERROR: database is locked: SQLITE_BUSY

in local development? im hoping this goes away when i deploy it...

Zig•5/29/25, 6:36 PM

Im running a pages app with D1 locally, and a DO thats accessed through both a DO binding in pages and a separate worker for the DO thats sometimes called by pages. The DO worker is ran with wrangler persisting the state to the pages worker D1 instance. The pages worker calls the DO to do some work and it modifies D1, the DO sends web socket messages to pages occasionally as it runs forcing pages to fetch D1 data.

I am getting seemingly random SQLITE and D1 errors that appear in random order, and arent confined to any one section of my code. Is this just a byproduct of trying to use 2 instances of wrangler, one with the persist-to flag on local environments? Or is this indicative of a problem with my usage patterns? Will this still happen on deployed instances?

Zig•5/29/25, 9:45 PM

Update: Deployed version works flawlessly. Guessing its some issue with 2 wrangler instances trying to use the D1 file at the same time

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 })

Well that proves the point, neither D1 nor DO solves the basic problems completely. Why would we sho

Similar Threads

Similar Threads

Similar Threads