Try datetime(crated_at, 'unixepoch') < datetime(<value>, 'unixepoch')?
Try datetime(crated_at, 'unixepoch') < datetime(<value>, 'unixepoch')?
HIIRC the current recommendation is to use SQLiteDOs
HDon't know whether that's the "official" thing or not
BDo SQLite DOs have the migration utilities that D1 does?
KThat results in no data being returned at all
I found out this bug only happens if I have the order by included in the query. If I leave it out the filtering works as I expect it too
I found out this bug only happens if I have the order by included in the query. If I leave it out the filtering works as I expect it too
BI'm pretty sure datetime converts into a string and you're trying to compare a number in the string in the first place and lexicographical strings in the second. Bad advice on my part - just omit the datetime altogether
BYou actually want unixepoch(created_at) < 1743526055
BYou should try out your queries in normal sqlite - I would be very surprised if the results differ from what cloudflare returns
HLike, via the CLI?
HIf that's the question, then no
KNever mind its all my fault
HIf you use an ORM, there is some tooling to make it a bit smoother
K< it should have been >K
SHey, wondering if anyone here has any tips or experience with this. Cloudflare charged my credit card a huge amount and I haven’t gotten a proper explanation from them, even after reaching out to support multiple times over the past two months. All I’ve gotten are generic “we’re looking into it” replies.
It’s gotten to the point where I can’t afford to pay the credit card bill, and it’s messing with rent and other important stuff. Has anyone had luck actually getting a real response from Cloudflare support? Or escalated it somehow?
And has anyone ever done a chargeback with Cloudflare? I’m seriously considering it because I don’t know what else to do.
It’s gotten to the point where I can’t afford to pay the credit card bill, and it’s messing with rent and other important stuff. Has anyone had luck actually getting a real response from Cloudflare support? Or escalated it somehow?
And has anyone ever done a chargeback with Cloudflare? I’m seriously considering it because I don’t know what else to do.
AI have this same question (d1-database). Are dynamic bindings coming anytime soon, or has anyone found a usable pattern within Cloudflare to dynamically select a database at runtime?
BYou can achieve dynamic SQLite databases with durable objects if that works for your use case, but dynamic bindings aren't avaialble afaik
KCloudflare API to create the database and a D1 worker as an API with the binding. Then drizzle proxy to the api. Once setup, it works and I get to keep D1 batteries included and continue to use drizzle as well. Not pretty but it works.
LIf you need to shard across tens thousands (or more) databases, please use SQLite DOs. Even if D1 ships dynamic bindings, it's not happening in just a few weeks. Use DOs that provide that scalability already.
The underlying SQLite features are identical.
The underlying SQLite features are identical.
Sis there a good example of this? at the end of the day you still need to bind the DO or am i forgetting something? running wrangler d1 create dosent seem like the issue to me personally
LYou only bind the DO namespace once, and create millions of Durable Object instances. With D1, you need to create each one individually and add it in your wrangler config and redeploy.
Swell yea with the downside of needing to run migrations on every Do invocation because you cant know if its a new do/db right? at least thats what i did with my DO better-auth example
LYou do know if you check the storage and keep in memory while your DO is alive. Not sure why you would run your migrations all the time. All SQL schema tools/libraries record what migrations they already ran and don't do anything if there is nothing new.
Shttps://github.com/Sillyvan/better-auth-do-example/blob/main/src/server.ts
id still assume something like this brings a bit of overhead? but its not too big of a deal of course!
id still assume something like this brings a bit of overhead? but its not too big of a deal of course!
GitHub
Contribute to Sillyvan/better-auth-do-example development by creating an account on GitHub.
AI appreciate the response! Does this mean that for the tenant DBs we would have different DOs for each one, but we would only have to use one binding somehow?
AForgive me if it's a dumb question, I haven't really used DOs but we have used D1 extensively
BYou could do something like the following for example where you have one Durable Object class in your wrangler binding (e.g. MY_DURABLE_OBJECT) but when you do the
So above I could change
idFromName you can pass something specific to the tenant you want. Each unique idSo above I could change
user_1 to be any of my users and I'd be routed to their specific DO instance.
AThat's helpful, thank you!!
LTake a look into https://developers.cloudflare.com/reference-architecture/diagrams/storage/durable-object-control-data-plane-pattern/ as well.
Cloudflare Docs
Durable Objects are built on-top of Cloudflare Workers spanning several locations across our global infrastructure network.
Each Durable Object instance has its own durable storage persisted across requests, in-memory state, single-threaded execution, and can be placed in a specific region.
Each Durable Object instance has its own durable storage persisted across requests, in-memory state, single-threaded execution, and can be placed in a specific region.
CWhy I'm getting database disk image is malformed: SQLITE_CORRUPT [code: 7500]
ABecause the database disk image is malformed
JHi all - Does a D1 batch() count as a single (1) sub-request against the Workers limit or are the individual transactions in the batch counted against the subrequest limit?
JThank you!
VI'm weirdly getting WAF bot detection blocked on
one of the rays:
api.cloudflare.com hitting the d1 /queryone of the rays:
92b3ef8f6aea1703-SJC
MHi @Walshy
MNice to meet you
MHaving a nice weekend?
MI need some advice.
MIs it possible to access coudflare d1 database outside of worker/page?
C?pings
SPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
CThe general recommendation is to deploy a worker which acts as a HTTP API for your D1 database. You can just use the barebones Cloudflare HTTP API but that is slower
MSo, I need to access Worker, not D1 database, right?
MHow can I get the url of Cloudflare D1 database, so that I can set the db attribute of Payload CMS backend?
C?d1-remote-connections
SAccessing D1 from outside workers:
D1 is based on SQLite, which does not natively support remote connections and isn't MySQL/PostgreSQL wire compatible, nor does D1 itself offer that functionality. As such, your options are:
1 -> The Cloudflare API Query Endpoint (https://developers.cloudflare.com/api/operations/cloudflare-d1-query-database), with the upside of needing less setup, all requests have to go back to Cloudflare's core, so request latency is far from optimal from some locations. You would also be subject to the API Rate limit of 1200 requests per 5 minutes.
2 -> Create a worker to proxy requests to your D1 Database. Either tightly bound to your application/schema or loose and just accepting any query. This would allow your worker to execute potentially closer to your D1 Database and avoid the api rate limit.
D1 is based on SQLite, which does not natively support remote connections and isn't MySQL/PostgreSQL wire compatible, nor does D1 itself offer that functionality. As such, your options are:
1 -> The Cloudflare API Query Endpoint (https://developers.cloudflare.com/api/operations/cloudflare-d1-query-database), with the upside of needing less setup, all requests have to go back to Cloudflare's core, so request latency is far from optimal from some locations. You would also be subject to the API Rate limit of 1200 requests per 5 minutes.
2 -> Create a worker to proxy requests to your D1 Database. Either tightly bound to your application/schema or loose and just accepting any query. This would allow your worker to execute potentially closer to your D1 Database and avoid the api rate limit.
MOh, you're smart.
MI think option 2 is good,.
MI tried with 'npx create-payload-app' project.
MBut the problem here is to implement admin dashboard
