LSo you've to use D1 for that with different concept. Cloudflare database (D1, DO) is broken. D1 has different limitation while DO has differentI 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.
P
this
WD1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset. .... Or just accept and move on?
A
1LThis is definitely different from the messaging that I've heard from other Cloudflare folks recentlyI 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
D
AL
H
S
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.A
GGGL
JJJJL
B
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.``
Record should be created with NULL for nullable fields (like amountUsd).
**Issue:**
Fails with JSON parsing error, even though:
- Schema correctly marks field as optional (Float?)
- SQLite table allows NULL (amount_usd REAL)
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. 
I
J
C
V
LGGCCC
ALI was thinking about implementing it in a project I'm working onDo 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.
ALA
B
A
P
SLL
.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.PPLPPD1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.PrismaClientUnknownRequestErrorPrismaClientUnknownRequestError: 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 })2. Schema (D1 DB):3. Attempted Query: ``
Record should be created with for nullable fields (like ).
**Issue:**
Fails with JSON parsing error, even though:
- Schema correctly marks field as optional ()
- SQLite table allows NULL ()
Here one thing to note (which is kind of weird) is that, once I try to insert .meta