In the changelog (only). Not a blog — we're in alpha and using this to make the changes we need.
In the changelog (only). Not a blog — we're in alpha and using this to make the changes we need.
Ngreat, will this be in workers change logs (https://developers.cloudflare.com/workers/platform/changelog/) or somewhere else?
JI'm getting "not authorized to use function" with timestamp functions (e.g. SELECT CURRENT_TIMESTAMP; fails). I'm using the new backend. Is this a known issue?
KKnown issue that'll be fixed in the next release
KJThank you
SAre there still known errors in conjunction with drizzle?
CThey did announce during dev week they will be increasing the size of paid plan size to 1GB 
CI don’t believe the 100 MB limit was raised anywhere due to technical limitations
ADrizzle works fine most of the time. Joins are a bit bugged due to downstream errors - https://github.com/drizzle-team/drizzle-orm/issues/528
SOkay, asking as I had some troubles yesterday mentioning prepare even though not using prepared statements. Will take a look after being back from vacation
MStarted getting a bunch of these again at 3AM CEST
MWe can increase some limits during the alpha — storage isn’t one of them. From the Limits page:
Note that not all limits can be increased.The original prototype backend just doesn’t perform well above 100MB. It’s pointless to increase it.
MWhich backend?
MExperimental
MGonna need more details than that. DB ID? What were you trying to do?
MID:
Error comes from first two POSTs here: https://github.com/leonlarsson/bfstats-api/blob/main/handlers/D1Handler.ts#L105
I'll try try dig up more info
e68dccd4-7bf7-4860-ba18-17978966ec10Error comes from first two POSTs here: https://github.com/leonlarsson/bfstats-api/blob/main/handlers/D1Handler.ts#L105
I'll try try dig up more info
MQuery looks pretty basic. Is this 100% of the time? 50%?
MMuch much less
MMaybe 2%
MLooking into if it's happening due to the username
MNope, nothing weird with the data. Just regular latin characters and short strings
MActually seeing errors from https://github.com/leonlarsson/bfstats-api/blob/main/handlers/D1Handler.ts#L152 as well, which the simplest query imaginable
MJust got the errors again on POST /d1/users and /d1/outputs
MDid you got any solution?
MYou should update to the latest wrangler first, especially if you’re not on v3+
MIt won’t be the queries. Yours are trivial. Likely a bug on our side. The new storage subsystem is still, well, new 
AYes, this is how I've done it
Ayour way is definitely cleaner than mine XD
HI think it is because
wranglertoml. They are adding a system to parse JSON into an object that wranglertoml spec, but there may be some points that don't just workHAnd which config format is the best is an extremely hot topic.
HWell, 
workers-rs), plus
wranglertoml. And you can still run Workers entirely without writing JS(see #workers-rs), plus workerd, which isn't JS at all. And they are moving toward JSON configs nowMI'm already on 3.0.1
MYes - 100MB is the limit for now. We aren’t increasing database limits yet. Hold tight.
MIt's definitely not an experimental database (I just got online and checked:
e68dccd4-7bf7-4860-ba18-17978966ec10 is on the older alpha backend)
MLooked at the wrong ID, ha. I see ~11 storage timeouts in the last 24 hours on that DB. This is related to a larger issue we're investigating.
MAhh okay
VHey there! It's feedback time! 
We would love to hear from you. What features do you wish D1 had? 
And what's your biggest challenge or frustration when using D1?
We would love to hear from you. What features do you wish D1 had? And what's your biggest challenge or frustration when using D1?
《My wish would be for more defined error messages. When executing a sql script. Often the error message is 'D1 Error' with no supporting information.
《Yeah, this is for wrangler sorry. Maybe wrong thread
UThat is valid feedback here also as its related to D1 still.
MWe're going to lift the errors out of
error.cause into the top-level error soon. It might break a few folks who are exact string matching: no real way around this. Luck of an alpha MHard to really schedule. Outside of an alpha it'd be a compatibility date, but we have to then carry that forever, and I'm going to lean on the "alpha" part of "alpha" here. Likely within the week. We're going to keep
error.cause around until open beta, then trim that up.MHi, is there any d1 orm except drizzle which support joins?
MI asked this because of this problem https://github.com/cloudflare/workers-sdk/issues/3160
Tried kysely. It works
Tried kysely. It works
GitHub
Which Cloudflare product(s) does this pertain to? D1 What version of Wrangler are you using? 2.19.0 What operating system are you using? macOS Describe the Bug As per issue #555 we can see, that d1...