We'll be increasing limits (on DB size and total # of DBs) over the coming months. Are you using Wor
We'll be increasing limits (on DB size and total # of DBs) over the coming months. Are you using Workers for Platforms?
MThanks. Looking into it. May not be a quick fix.
DI might be 
MD1 Beta doesn't like it either 
MMCoincidence or not, I just got the same error in a completely different place: https://github.com/leonlarsson/bfstats-api/blob/main/handlers/D1Handler.ts#L58
JTrying to load my alpha db dump into the new backend via wrangler, with 27k or so lines, first just hung as it did for @mozzy , tried breaking into a file with 4999 lines, now getting
JTried pasting entire 27k sql lines into the web console, after a minute or two all the statements showed up in the console but the last line is again:
statement too long
NI'm confused about the db size limits. The blog says in the pricing that 1GB is available to free users and 5GB included and $0.75/GB beyond that.
But then it says "Developerson the Workers Paid plan will get access to 1GB dbs in the very near future".
Does this mean that the limit is currently still 100mb, will soon be 1Gb and later will change to what the pricing shows?
But then it says "Developerson the Workers Paid plan will get access to 1GB dbs in the very near future".
Does this mean that the limit is currently still 100mb, will soon be 1Gb and later will change to what the pricing shows?
Bmaybe a better approach would be dbs per regional area
Bwhen a user creates their account, pick a db based on their geography to route to, and always use that db for that user
Bdepending on how far you want to take that, you could do an NA region, EU region and Asia region for example, or more
BLocation Hints will allow you to peg where the write region is placed
IYes. Limit is still 100mb, will be raised to 1GB, and then likely further eventually.
IYes it's possible but undocumented as far as I know (and the API is slower than D1 from a Worker)
UCurrently in alpha it is free to use and limited to 100mb. In the future those payment plans will come into play and the limits for dbs will be higher
II(think those endpoints should still work)
NThanks! Very exciting stuff
MYep, you can bind to a D1 DB from multiple Workers, just like Queues/KV/R2/etc.
JLooks like it was one of the statements in my dumped/converted .sql file that was inserting a very long binary blob and this was throwing the error. If I skipped that insert statement, the rest of it imported alright
MAny ideas what might be causing this or a way to debug this issue a bit more? https://github.com/cloudflare/workers-sdk/issues/3294
GitHub
Which Cloudflare product(s) does this pertain to? Wrangler What version of Wrangler are you using? 3.0.0 What operating system are you using? Windows Describe the Bug create a fresh D1 local DB wit...
MHow long? https://developers.cloudflare.com/d1/platform/limits/
- I bet you hit the max row length with a big blob. Would be helpful to know so we can think about adjusting over time.
J267k characters
Joh yeah i see the max statement length is 100kb
JIt's interesting that it let me insert that row initially from within the worker, but not via wrangler or the console
M- Right now, deletes are treated as writes. Subject to change. Unless you're deleting a LOT of data, all the time, I'd be very surprised if your write+delete costs on D1 exceeded DO.
- No limit on tables, but any table is non-zero bytes (to store the schema and allocate storage for an empty table). If an empty table is ~4KB or so you could have thousands of empty tables with no data, if you really desired to do so
MDamn, I'm not even able to return a single column now :(
SELECT date FROM outputsMDid the sensible thing and stopped relying on the bigger endpoints and instead created a few more specialized ones
UThere will be some limit which right now is on the lower end but they are working on increasing it... which I assume the new backend has increased that a good amount given what I read from the blog
IDO has somewhat different goals than D1 so I expect they will continue to exist.
IDO = global "actor" model, there will always be one unique actor per ID/name in the world, that actor has access to key-value state
D1 = a "database", with tables/rows/columns etc.
D1 = a "database", with tables/rows/columns etc.
UIts friday night and this is an alpha product so I doubt anything will be done until monday when they are back at work.
