I say use a JOIN, that is what it's intended for. No need to JOIN datasets "in code", databases e
I say use a JOIN, that is what it's intended for. No need to JOIN datasets "in code", databases engines are optimized to handle joins efficiently.
TThank you! Is this applied to SQLite? I'm using D1 btw
TThank you! I'm kinda new with SQLite
AI know read replicas are coming soon, so assume currently there is just a leader being created, but what happens if the DC the leader is in goes down? I assume right now the DB would be inaccessible... but in future, would a new leader be elected in the event a region/DC goes down where a D1 database's leader is?
MThis is already the case. We run the leader from another data center in the same region implicitly.
AAwesome, thank you!
Mhttps://developers.cloudflare.com/pages/framework-guides/ and https://developers.cloudflare.com/d1/examples/
- D1 is just like KV
Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites
MThe guides show you how to bind a database using Pages.
M(I strongly suggest following one of the Pages tutorials first) 
CAre you passing a D1 binding with your pages dev command?
Cshould I switch to new D1 backend? 
Cit doesn't have back up yet
MScrew backups, live on the Edge (of your seat)
CTime travel is available d1-database
Hi switched my production database to d1 and were finally live on the edge (of my seat)
Mhmm... this doesn't seem right...
trying to use db within a pages function works locally but dead in prod for me. anything im missing?
trying to use db within a pages function works locally but dead in prod for me. anything im missing?
Mi did forget to add the binding, but also did a new deploy after adding it to preview env
Wwhat does "dead" mean in this context?
Are you trying to use it in a prod deploy? If so, you'll want it in the Production tab too
Are you trying to use it in a prod deploy? If so, you'll want it in the Production tab too
Mumm no was just missing the binding in context, but turns out i was still using the last deploy's url 
Whaha that'll do it
Mcompletely user error 
AI've been experimenting with D1 on and off now for a few months. A few months ago I had set up a database, and it was working perfectly fine. I took a few months off of that project and worked on some other things. I've now come back to that project with D1 and now this request to D1 is failing and im not sure why. Any ideas?
Anevermind. turned out to be a structure migration that replaced something that it shouldnt have, causing an invalid SQL statement. Would be nice to have better errors though (at least an "invalid SQL statement" would have turned this from a 5 minute investigation to about 30 seconds )
)CThat only works in production. From the docs
Pass the --d1=BINDING_NAME flag when developing locally. BINDING_NAME should match what call in your code
BHi all, even though D1 is in alpha, I am considering using it for a new startup (hoping D1 would be beta around the time the MVP is ready). Worst case scenario is that I would have to migrate to another database before official launch (to avoid migration headaches early on). BUT I would need JS transactions. Is there any insight / timeline into the complexity of this feature? How likely will it be delayed? Is it the next focus, or are there other major changes / features coming first? I understand this is hard to answer, so "We don't know" is perfectly valid too of course!
SHas there been any indication when D1 will move from public alpha to public beta? I noticed it was on the roadmap in the last blog post but they didnt mention timing. Would love to plan my team's next solution around SQLite and I feel like D1 has the best DX out of all the available options. Just hard to sell it when there's all the alpha disclaimers everywhere.
MJS transactionssupport for SQL transactions in the JS API? if so, look into
db.batch (https://developers.cloudflare.com/d1/platform/client-api/#batch-statements)As part of our Client API, both static and prepared statements are supported. Best practice is to use prepared statements which are precompiled …
BI would love to integrate D1 with kysely, according to the author of kysely-d1, integrating with the 
see: https://github.com/aidenwallis/kysely-d1/issues/2#issuecomment-1327869881
batch API is not feasible for this see: https://github.com/aidenwallis/kysely-d1/issues/2#issuecomment-1327869881GitHub
Transactions are not currently supported in D1. Once they are, this package needs support added for them.
FHi all, is there a way to restore a D1 from a backup? I have 2 databases - one has some data and the other is empty. I am trying to copy all the data from the first to the second. I was hoping that I could export a backup from the first one (which I was able to do) and then use the restore on the second (and hope to 'clone' the first it into the second - including structure and data)
Ccloudflare has built in backups on experimental backend.
edit: i was confused, backups are normal, time travel is on experimental
edit: i was confused, backups are normal, time travel is on experimental
CD1 allows you to import existing SQLite tables and their data directly, enabling you to migrate existing data into D1 quickly and easily. This can be …
FThanks! I'll have a look. I knew about the Backup function, I just could not find the Import from an external backup.
Min
wrangler.toml, why do we need to specify database_name? it seems redundant, given that you specify the database IDM(could also be a question for #wrangler , just lmk and ill move this over there)
Mit probably wasn't well thought out tbh
Mmuch like how we have envs in wrangler.toml but also preview_database_id
KAt least D1 doesn't error if you don't specify a
preview_ :^)
Hyeah with r2 i had to specify a preview for any env that is not at the top level configuration of wrangler.toml
Hwhich i just set to be the same as the top level bucket anyway 
KYeahhh, it's not the best
Mah I see
Mwow the beta backend is incredibly fast compared to the alpha backend
Jnew D1 backend be zoomin' yeah, it's such a wild improvement
Myeah I did a double take because I thought they just changed the units in wrangler from
ms to s, but no, the query really did only take 0.3msMdoes
stmt.raw() return an empty array or null if there are no results?