> (To answer my own question, apparently Azure SQL does) Which is fun when you add a future schema migration that drops a column, test in locally and in some t

> (To answer my own question, apparently Azure SQL does) Which is fun when you add a future schema migration that drops a column, test in locally and in some test cases, and then see it bomb in production because the column has an Index that you weren't aware of. (That's an easy thing to solve though, but definitely one of those cases where "The database is messing with its schema on its own" does do funny things)