My Notes

Can’t understand how migration rewrite is intended to be used

Successfully did a migration rewrite on a database I had previously migrated via CLI migration tool. (Is that a no-no?)
Now I can’t migrate anymore
- There is no database revision m1vgbp4v6vdosioznyjya6re5pygidpdf2txt2427qdzjsp3p5q7wa in the filesystem. Consider updating sources.
migration files were still in place
- Tried deleting them, and it didn’t help
Describe migration as DDL and don’t commit, or commit to rewrite migration history
Treat it as the other migration commands
- Draw inspiration
Workflow
- start migration to
- system compares schema in database to the one you’re migrating to
- When you run describe current migration (as json usually), it suggests DDL
  - Gives you the part that has already been accepted
  - Then it asks you to confirm its proposals, reject for another proposal, or provide custom DDL
  - Works as long as the result matches the current state
- You can agree or reject because the system may not interpret the change correctly
- Can reach an impossible state because you have rejected too many possibilities
- populate migration skips the steps; tries to run migration without intervention
May need a guide

Feature freeze and beta ship next week (possible/probable?)
- May or may not support pg_dump with 3.0