I wonder if you can use a db.batch in your worker and have your pragma foreign key as the first stat
I wonder if you can use a db.batch in your worker and have your pragma foreign key as the first statement
MI was going to try a workaround like that, but it's still not ideal because I can't use prepared statements that way
MCF must have somehow set foreign_key default on for the alpha backend, so it'd be really nice if they could expose an option to allow that same behavior for the beta backend
MIf I have some extra time this afternoon I might file an issue on the github repo
Kforeign key default is set on the experimental backend 
Kor it might be soon
Kit was committed to workerd 2 weeks ago so it'll be in the next release if it hasn't already released
MRight, for the experimental backend:
- all queries run inside a transaction
- You can’t enable foreign keys via the PRAGMA inside that context
- We are making foreign key enforcement the default
- You can relax it with
PRAGMA defer_foreign_keys = on - Docs coming very very soon
MThank you! I'm glad this is on the radar and coming soon.
MWIP docs: https://silverlock-d1-foreign-keys.cloudflare-docs-7ou.pages.dev/d1/learning/foreign-keys/
Need to write up FK actions, add basic schema examples (how to define fkeys between tables), and how to handle errors/resolve FK issues - before I publish it proper.
Need to write up FK actions, add basic schema examples (how to define fkeys between tables), and how to handle errors/resolve FK issues - before I publish it proper.
Mjust realised we pretty much never actually want to set a default value in the form based on the field's sql default value, since it needs to be NULL for sqlite to use the default value
BLooking to integrate honeycomb.io with d1 to get traces of db queries in my logs. Anyone already done something like this?
Thi guys, I'm having two table
document and document_type and document has a foreign key of document_type. document is a relatively large table and document_type has 10 or 20 records. What should I do when I want to get data from both tables, using JOIN or SELECT two times and use code to get the final data?
LI 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
batchGitHub
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 …
