is this safe? are all of our migrations idempotent? I faintly remember doing this manually and was getting errors on various migrations so I had to find the actual version right version to start from
well we should at least test for sqlite and PG reseting various snapshots back to base and then doing an instance migrate.
It just seems odd to me that if create my DBs at 0.10.0 and then do this reset the instance migrate, I will play like the 0.6.0 migration. I guess we can update all the migration code to ensure they do some check before running forward
The specific migration revision is a bit tricky, because you could have three different physical dbs for the different storages, all with a different alembic version.
You could also technically be using sqlite for one and postgres for the other, which would have a different set of valid revisions. It'd be way easier if we just had a single storage concept with a single version id.
Not sure how much complexity we want to expose here, and if it's worth going through (the current state is that we manually tell people to drop the appropriate table).
impressive spelunking. This seems like an improvement overall, sorry it took so long for me to get back to it
did you update the quip to reflect this / will a test break if you create a new migration and don't update this?
check out test_alembic_up_to_date in the internal repo for a way you might accomplish that
consider naming these differently (runs/schedules/event_logs) the module helps but it seems easy to accidentally swap in the wrong one