I don’t *think* SQLite supports more than one query in a prepared statement
I don’t think SQLite supports more than one query in a prepared statement
KThat’s what the documentation would lead me to believe anyways
KYou’ll probably want to split those up into separate prepared statements
SThanks
Wenv[data.db].prepare...
EHow can I share permission with another cloudflare account for D1? I gave "Workers Admin" permission to other account but it gets "Authentication error (Code: 10000)" error when click D1 page. Workers page is fine.
MD1 isn't in the Workers Admin permission at the moment, it's coming very soon though
EDo you have chance to share ETA? I got a job and client only wants to use cloudflare. Client's is not giving account access just permissions.
EOr will administrator works?
MAdministrator will work, ETA is as soon as next deployment happens
Mare you getting an error?
Mdo you have the Workers Admin role, by any chance?
Min cloudflare's dash -> manage account in the bottom left corner -> click members
Mif you're not the administrator of the account, that could be causing issues
WYeah I'd type in your data but yeah
Mif you give your d1 dbs a prefix like
D1_, you could do something like Object.keys(env).filter(key=>key.startsWith('D1_'))Motherwise Object.keys will give you everything on env, not just your d1 dbs
DHi! I wonder about the result object returned from from stmt.all() and .run(). Is it possible that it returns { success: false, ... } without raising an exception?
NHi there, I'm quite interested in D1, but of course find the 100mb quite lacking. Obviously that's an alpha restriction and I'm not concerned about timelines, but somewhere here it was said this is due to a technical limitation because it loads the entire SQLite DB into memory.
My question is whether that (loading into memory) might change in the future? Because, if not, it seems like D1 could only ever be for very small applications (or cost a fortune to pay for GBs or even TB of ram...).
Thanks!
My question is whether that (loading into memory) might change in the future? Because, if not, it seems like D1 could only ever be for very small applications (or cost a fortune to pay for GBs or even TB of ram...).
Thanks!
Mwe're very aware 100MB is limiting - looking at higher limits for beta
Mdoes it work without the numbered params? as in just
?think there's a bug in miniflare
NYes, sorry, I'm aware that you're aware. My question is whether it will change to not load the entire db into ram, so that large dbs could be possible and affordable? If so, I'm happy to work within the alpha and beta limits. But otherwise, there's no point in me dedicating time to this if it won't be possible/affordable to use D1 in production
Mnot sure yet tbh, next goal is at least a gig
NOk. I suppose I'll just keep an eye on this then. What I'm curious about is not what the limit will evolve to be, but whether it will be tied to ram (expensive and size-limited) vs ssd (cheap and unlimited in size). If there aren't currently any plans to consider moving out of ram, I can't justify testing D1
NI'm sure it'll be a wonderful solution though for many smaller applications!
