database_id and preview_database_id in wrangler.toml
database_idpreview_database_id
C
S
II
I
R
L
last_insert_rowid() https://www.sqlite.org/c3ref/last_insert_rowid.html. That would allow you to insert one child with the parent. If you really want to insert more than one, then do the child inserts into a temporary table and delete as you move over to the real child table. I'm sure you could find an example of this on Stack Overflow. The second alternative would be to use a GUID that you generate client-side for your primary key. That doesn't take advantage of SQLite's really cool auto-increment rowid capability but that's really a nice-to-have.IThe AUTOINCREMENT keyword imposes extra CPU, memory, disk space, and disk I/O overhead and should be avoided if not strictly needed. It is usually not needed.
I
T
T
created_at column since most of tables are required to be sorted with created_at descending.
J
JJR
JJ
R
R
I
IT
PRAGMA foreign_key=off since the last time I update my table it was a nightmare
K
M
MM
M
J
S
B
MMJ
AA
V
RWorkers with a D1 binding will always be placed in a data center near the location of the D1 database they are bound to. Subrequests to other back-end services are ignored by Smart Placement in this case.
https://developers.cloudflare.com/workers/configuration/smart-placement/#d1
VRV
MMMMM
IIV
last_insert_rowid()created_atcreated_atPRAGMA foreign_key=off