There is not a transactions beta. What are you trying to do / how do you want to use transactions?
There is not a transactions beta. What are you trying to do / how do you want to use transactions?
EI have a whole bunch of database updates attached to a workers call that need to run atomically.
MToday the approach for that (if it fits your use-case) is
db.batch (or UPSERT / ON CONFLICT) - there is not a way to ship a transaction to D1 outside of that.EWhat about D1 procedures? or is this article too outdated?
https://blog.cloudflare.com/whats-new-with-d1/
https://blog.cloudflare.com/whats-new-with-d1/
The Cloudflare Blog
Get an inside look on the D1 experience today, what the team is currently working on and what’s coming up!
MLots of core stuff to build before we get there. We're prioritizing read replication + performance + stability first.
EMakes sense. I'll look into
db.batch for now.
Cquestion regarding setting up a database which creates the best space savings for a field when nothing is set:
a. email TEXT
b. email TEXT DEFAULT ''
a. email TEXT
b. email TEXT DEFAULT ''
Cso if nothing is set in the email in part a, the field would be filled with "NULL" just wondering if behind the scenes that takes up more space than choice b
Dwhat is the best practice for adding a column to an existing D1? Is the Alter command from wrangler the only method currently supported or are there any other methods such a Console from the Dashboard?
C@Matt just wondering if you had any incite on the "under the hood" storage of how D1 saves things, is there more saving a field as "null" or 0 character string?
UI dont think you should be that worried about saving a few bytes an item like that tbh just do whatever you think best for your application that makes it easy for you to manage 
Cthe OCD in me does worry...so would be good to know!
K
Care you sure the way Standard SQL lite does thing behind the scenes i the same as how D1 does it? I don't think its always a 1 to 1 situation...only the cloudflare wizards would know what lies beyond the veil
Cso that means...its basically the same size?
Chttps://www.sqlite.org/fileformat2.html#record_format or i mean a someting wit a content length of 0 is Null?
CAnother question regarding fields, i have a field set to:
time_stamp_updated INTEGER DEFAULT CURRENT_TIMESTAMP,
If I make an entry and don't set this field, it sets it to:
2023-09-26 17:40:44
I was thinking it would set it to to the epoch time similar to Date.now() which would be an integer like: 1695750044698
When going to dashboard and then attempting to update, an update can't occur because the dashboard flags the entry at that time_stamp_updated area.
That said, it still saved "2023-09-26 17:40:44" which is not an integer...how did it do that?
time_stamp_updated INTEGER DEFAULT CURRENT_TIMESTAMP,
If I make an entry and don't set this field, it sets it to:
2023-09-26 17:40:44
I was thinking it would set it to to the epoch time similar to Date.now() which would be an integer like: 1695750044698
When going to dashboard and then attempting to update, an update can't occur because the dashboard flags the entry at that time_stamp_updated area.
That said, it still saved "2023-09-26 17:40:44" which is not an integer...how did it do that?
CAlso noticing workers sets Date.now() to something like 1695750600382 while D1 sets unixepoch('now') to 1695750600
IDate.now() is in ms, SQLite is in secs.
Cwondering if that would make sense if they were more aligned to both either be in ms or secs?
IIt might, but that would deviate from SQLite behavior, which I doubt they'd want to do.
IIt would mean every time someone imported a SQLite database the user would need to know to convert manually.
Ctrue
Cperhaps the D1 wizzards could deviate slightly and created a new unixepoch function ie, unixepochD1
Cthat would use ms, given the environment its used in
Cidk maybe its a silly idea
Ci am going to set time_stamp_updated INTEGER DEFAULT (unixepoch('now') * 1000) to aleviate confusion
Mtimestamp_updated_ms - give your names units
Chow would one define that...? I tried time_stamp_updated INTEGER DEFAULT (timestamp_updated_ms('now')) AND time_stamp_updated INTEGER DEFAULT timestamp_updated_ms
Cbut no success
Cor are you just saying label it with the expected units?
M^ that. Give your column the name of the units it contains. Not a requirement - just a tip
Cgot it! I just set it via: time_stamp_updated INTEGER DEFAULT (unixepoch('now') * 1000)
Cto normalize things which works for mee
Cbut that said, if setting time_stamp_updated INTEGER DEFAULT CURRENT_TIMESTAMP, i think wrangle should flag that as an error
Cwith type mismatch of some sort given CURRENT_TIMESTAMP will save a non integer result
wrangler could check for that when the following line is executed:
wrangler d1 execute <DB_NAME> --file=dbtablecreate.sql
wrangler could check for that when the following line is executed:
wrangler d1 execute <DB_NAME> --file=dbtablecreate.sql
Cwrangler could check for that when the following line is executed:
wrangler d1 execute <DB_NAME> --file=dbtablecreate.sql
wrangler d1 execute <DB_NAME> --file=dbtablecreate.sql
Chttps://developers.cloudflare.com/vectorize/ seeing this in the realease notes (3.10)...but its a dead link
MWhich specific math functions?
MMGitHub
The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd
KHave you actually used
COS (i.e all caps) or cos?KHmm.
KI might just be blind, but I don't see anything in workerd indicating that it even has the maths functions enabled.
K