TSame error:
D1_ERROR: internal error; reference = 3v37q0sukf03r4emb40aq73q , account_id: 75d8d68ecf8f9e8155f1ccc7dad82e00
J8863216c46bc0b22436dac7ad793a08f
JAny progress? Thanks a lot
BI store base32 and base64 strings within sqlite. It would be nice if D1 supported extension functions to encode blobs as base32/base64 / decode base32/base64 strings (akin to hex/unhex that do the same)
BIt just makes it more convenient when running queries directly to debug stuff vs having to write JS to interpret the DB.
HWrong channel? This is for D1, the database
AHey Team, I am based in Sydney Australia, and trying D1 + Cloudflare pages using Drizzle ORM.
I am experiencing, each DB Call takes at least > 230 miliseconds.
I found multiple forum, people discussing D1 queries taking time. (I have created indexes, but that should not be a problem, since my DB is very small , with few test data in KBs).
Is this latency due to D1 not closser to my Pages Worker?
I am experiencing, each DB Call takes at least > 230 miliseconds.
I found multiple forum, people discussing D1 queries taking time. (I have created indexes, but that should not be a problem, since my DB is very small , with few test data in KBs).
Is this latency due to D1 not closser to my Pages Worker?
1Smart Placement might help, are your requests going to the Sydney colo or elsewhere?
BHi, if you have multiple workers needing to talk to the same d1 instance when doing local development? How do you achieve that?
If I run both workers, they each create a
If I run both workers, they each create a
.wrangler directory with each state independant from each other. Thanks
J'persist' option on wrangler when you run it, pick one dir for both
Ahow to figure out, where request goes when we query D1 database?
1In the response from the Worker, look at the
cf: colo headerAThanks, I get-
Isn;t it about the location of pages or worker? I am curious about my D1 DB location where read happens, I guess for each query to take >240s, it seem it is network latency.
Isn;t it about the location of pages or worker? I am curious about my D1 DB location where read happens, I guess for each query to take >240s, it seem it is network latency.
Sif you scroll up 5 messages theres your answer x)
LEvery D1 response now has a
To get the location of your worker, as others mentioned above you can use Cloudflare headers of the request telling you the
Or fetch the URL https://cloudflare.com/cdn-cgi/trace from within your worker and check the
meta.served_by_region information. That's the location (region) of your database instance that processed the query.To get the location of your worker, as others mentioned above you can use Cloudflare headers of the request telling you the
colo: https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfpropertiesOr fetch the URL https://cloudflare.com/cdn-cgi/trace from within your worker and check the
colo= line.
LWhat does "build an SQLite database separately" mean? You mean uploading an existing SQLite database file?
If yes, you can use the import API: https://developers.cloudflare.com/d1/best-practices/import-export-data/
If not, I don't understand the question, so please elaborate.
If yes, you can use the import API: https://developers.cloudflare.com/d1/best-practices/import-export-data/
If not, I don't understand the question, so please elaborate.
AI mange to find DB location from command
wrangler d1 info <db_name> , which tells me my db is in Wesern north america, while the only time i ussed it ws from AU. Now I am moving my DB Back to AU by creating new db/exporting data to it.Acommand
wrangler d1 export --remote <db_name> --output=x_backup.sql does not create DDL & DML in correct order. (Table being referred get created later.).
TPretty sure the answer to this is no. Cloudflare announced some D1 changes last April. Maybe they'll have more updates around the same time this year.
J▲ [WARNING] No migrations folder found. Set
i;m getting this error why?
PS : Solved it, was a stupid fix
migrations_dir in your wrangler.json file to choose a different path.i;m getting this error why?
PS : Solved it, was a stupid fix
Ji already set up the path
くIs it possible to do something like enum type with d1?
Jsqlite doesn't support enums directly, but you could use a
CHECK constraint on your column to accomplish a similar result.
DMake a not null foreign key constraint to an enumerated table 
Ayeah they bank a bunch of updates for developer week each year
Aim personally hoping for some replica news, but we'll see
THoping for larger max size of databases or some easy way in workers to dynamically access many databases I shard accounts to...
Dhiep@MBP-Hiep payalert-backend-v2 % wrangler d1 execute pay-alert --local --file=./database.sql
✘ [ERROR] Could not read file: ./database.sql
Cannot create a string longer than 0x1fffffe8 characters
HELP: database sql file 2GB
✘ [ERROR] Could not read file: ./database.sql
Cannot create a string longer than 0x1fffffe8 characters
HELP: database sql file 2GB
DHello! I am using a D1 database and have golang script for upserting some rows in D1.
The cloudflare-go sdk that i am using is v0.89.0.
Everything worked good until last Monday that i started getting this error:
failed to upsert customers to D1 {"error": "error from makeRequest: received internal server error response (HTTP 500), please try again later"}
Any known issue or api change?
Wasn't able to find a relevant changelog
The cloudflare-go sdk that i am using is v0.89.0.
Everything worked good until last Monday that i started getting this error:
failed to upsert customers to D1 {"error": "error from makeRequest: received internal server error response (HTTP 500), please try again later"}
Any known issue or api change?
Wasn't able to find a relevant changelog
LIf you query your database directly or through the dashboard UI console does it work? That error message is not a D1 error so not sure which layers fails for you there.
Dyes quering the d1 directly from the Ui console works.
I have noticed some other api compatibility issues that i have fixed.
My code was originally like this:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery.String(),
// error was originally here
})
The first error that i started getting was this:
Invalid property: params => Expected array, received null (7400)"}
When i changed the code to include a string array with params i started getting:
failed to upsert customers to D1 {"error": "error from makeRequest: received internal server error response (HTTP 500), please try again later"}
This started happening one week ago.
I have noticed some other api compatibility issues that i have fixed.
My code was originally like this:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery.String(),
// error was originally here
})
The first error that i started getting was this:
Invalid property: params => Expected array, received null (7400)"}
When i changed the code to include a string array with params i started getting:
failed to upsert customers to D1 {"error": "error from makeRequest: received internal server error response (HTTP 500), please try again later"}
This started happening one week ago.
LWe recently added some validation on that endpoint. The
I will see if we can make the
Invalid property: params => Expected array, received null (7400) seems to be coming from that validation. The params is an optional list argument that should only be provided if you have bind parameters in the SQL query.I will see if we can make the
params === null be treated the same is not provided at all, since null is not a valid value per se for that list argument.When i changed the code to include a string array with params i started getting:Not sure what you mean here. Did you provide an empty slice?
DI mean i fixed the 7400 null error by passing an empty string array. But after fixing this error i started having the ""error": "error from makeRequest: received internal server error response (HTTP 500), please try again later"}"
Ahi! can someone confirm that "bound parameters" refers to the total number of args passed into the query?
A*number of placeholders
LThe SDK docs explicitly mention that non-provided fields are not sent: https://github.com/cloudflare/cloudflare-go/tree/main?tab=readme-ov-file#request-fields
Weird that in your case @dimsid
Can you upgrade your SDK version used to https://pkg.go.dev/github.com/cloudflare/cloudflare-go/v4#section-readme and try that?
All request parameters are wrapped in a generic Field type, which we use to distinguish zero values from null or omitted fields.
This prevents accidentally sending a zero value if you forget a required parameter, and enables explicitly sending null, false, '', or 0 on optional parameters. Any field not specified is not sent.
Weird that in your case @dimsid
null is being sent for params. Did you not provide it at all (as your snippet above implies), or did you provide it explicitly as null?Can you upgrade your SDK version used to https://pkg.go.dev/github.com/cloudflare/cloudflare-go/v4#section-readme and try that?
DLet me rephrase my problem so that i can be clear!
I have a golang script using cloudflare-go sdk version 0.89.0.
In my scipt there was this code:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery,
})
and it was working.
Last Monday 3 March 2025, this script stopped working, with this error:
Invalid property: params => Expected array, received null (7400).
Following the error message, I updated my code to this:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery,
Parameters: []string{},
})
and the 7400 above was gone but a new error ocuured which is this:
error from makeRequest: received internal server error response (HTTP 500), please try again later
And I am wondering if except from the validation check you mentioned, something else also changed and my query does not work.
As mentioned i am using sdk version 0.89.0 and I would not like to make a version upgrade to v4 if possible
I have a golang script using cloudflare-go sdk version 0.89.0.
In my scipt there was this code:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery,
})
and it was working.
Last Monday 3 March 2025, this script stopped working, with this error:
Invalid property: params => Expected array, received null (7400).
Following the error message, I updated my code to this:
res, err := c.api.QueryD1Database(c.ctx, cloudflare.AccountIdentifier(c.cfg.Cloudflare.AccountID), cloudflare.QueryD1DatabaseParams{
DatabaseID: c.cfg.Cloudflare.DBID,
SQL: sqlQuery,
Parameters: []string{},
})
and the 7400 above was gone but a new error ocuured which is this:
error from makeRequest: received internal server error response (HTTP 500), please try again later
And I am wondering if except from the validation check you mentioned, something else also changed and my query does not work.
As mentioned i am using sdk version 0.89.0 and I would not like to make a version upgrade to v4 if possible
LAs I said, there is a new validation now on our API for that endpoint. The error you get
I already made an improvement to allow
I do suggest upgrading at some point though to make sure you get the improvements of the SDK.
Invalid property: params => Expected array, received null (7400) is from that validation. That old version of the Go SDK I believe sends null when it should not send anything.I already made an improvement to allow
nulls for now for these cases, but it needs some time to be rolled out.I do suggest upgrading at some point though to make sure you get the improvements of the SDK.
DHello thanks for all the replies! As i described above the 7400 error was fixed. What about the "error from makeRequest: received internal server error response (HTTP 500), please try again later"
LIt's not fixed really. By passing empty array you trigger some other flow to fail since the params should not be empty. That's another thing to be fixed somewhere across the path, either in the SDK or the API itself to return a proper error instead of 500.
I am rolling out the validation fix to not fail with
I am rolling out the validation fix to not fail with
null for now so your original code should continue working once that's out everywhere.DThank you! I would appreciate if you could let me know with a reply here, when this is rolled out
LShould be complete now. Please let me know if you still get that validation error.
DThanks a lot for all your support! it is working now