A
L
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
LGG
CCC
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
.metameta
ZD1_ERROR: Failed to parse body as JSON, got: Error: internal error; or D1_ERROR: database is locked: SQLITE_BUSY in local development? im hoping this goes away when i deploy it...ZPrismaClientUnknownRequestErrorPrismaClientUnknownRequestError: 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 D1_ERROR: Failed to parse body as JSON, got: Error: internal error;D1_ERROR: database is locked: SQLITE_BUSY