Bad migration detection in multiple database setup
|Reported by:||Claude Paroz||Owned by:||nobody|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
While trying to play with migrations in contrib apps, I stumble upon test issues, and finally found out that the migration was only applied to the first database ('default'), because while setting the second test database ('other'),
MigrationRecorder was querying the first (default) database to detect if the migration was applied or not.