There are absolutely ways to view the instances and view what's in the databases. Unsure where that
There are absolutely ways to view the instances and view what's in the databases. Unsure where that idea comes from exactly
This 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
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 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.
.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.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.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