Each migration needs to live on its own PR

Separation of PR can make PR roll-back pure and easier when something goes wrong

• Especially when there is a data migration involved vs schema migration

Split by natural boundaries

• part1: migration 1, related scope 1
• part2: migration 2

Dropping References

Don't drop references without gradual approach

• Ignore column first, then → Drop column
  • Should be separate migration to prevent deadlock