Got it, that's good to know π . I suppose once backups are available it makes sense to switch then
Got it, that's good to know
. I suppose once backups are available it makes sense to switch then
--fork/--clone approach and make overwriting (even more) explicit.--minutes-ago=15m or similar to avoid you having to deal with Unix timestamps.
--clone/--fork --clone=new-nameNow, you clone it out for initial data. You run things for a while and then you want to revert. Now you have to go and change where each of those things point to (by cloning the "backup" to a separate thing, because otherwise you loose it).
id (in line with kv format), but then the example uses database_id. Which one is it?
database_id id SERIAL PRIMARY KEY seems not work, I follow the doc https://developers.cloudflare.com/workers/tutorials/postgres/#5-interact-with-the-products-database, I know the condition is own host PostgreSQL but the D1 should be the same, right?

id int primary key autoincrement --fork/--clone--minutes-ago=15m--clone/--fork--clone=new-nameiddatabase_iddatabase_id id SERIAL PRIMARY KEYid int primary key autoincrement