My Notes
- Automate restoring deleted migrations?
- Document Postgres version support?
- https://edgedb.slack.com/archives/CNECHA9EW/p1693306508247509
- Aljaz gave me a partial table showing 3.x and 4.x
- Add field for Postgres version to the bug report template?
- If so, on which repos?
- Dev instance or custom deployment?
edgedbrepo only
- Notifications on build failures?
- Do they go out? Can they be more effective?
Meeting Notes
- Official stance on rolling back migrations
- Elvis: Ideally, we generate forward and down migrations simultaneously
- Reuse guidance when we ask questions to allow for simultaneous generation
- Down migration needs a reverse of statement to generate values when going from required to optional
- Elvis: alternatively, make DDL reversible
- more fundamental change
- Sully: more work but more likely to work
- Now, in development, just make a migration that reverts the previous one
- In production… don’t deploy to production if you haven’t tested
- Maybe supports bad practices
- Could hide some implications
- If you delete a column, you can’t undo because the data is gone
- If you add a column and revert, whatever data you wrote to it is gone
- Maybe side-by-side migrations are more interesting if we want to devote time to that.
- Elvis: Ideally, we generate forward and down migrations simultaneously
- Find a plugin that will notify in Slack on nightly build failures Todo
- Tie to git blame and pester the person who added a test
- Sully: automate a retry first?
- Elvis: fix flake instead of just retrying
- Check nightly builds periodically Todo