Order of settings and transactional_db fixtures

I use both in my tests and I created a media fixture (creating a temporary media directory and using the settings fixture) with autouse=True, due to alphabetic order it made the settings fixture run before the transactional_db fixture, but my post_migrate handler creating basic models depend upon the settings, in a test testing modification of those settings the teardown of transactional_db calling the flush() run with the modified settings instead of the default settings, modifying the default state of the database.

I think that a way of forcing run of setting before transactional_db must be found, as the post_migrate handler can depend upon the settings.

Start by reproducing the interaction between the autouse media fixture, the settings fixture, and transactional_db, focusing on the post_migrate handler and transactional_db teardown flush(). No file or test path is named in the issue. Done means modified settings no longer affect teardown database restoration while settings-dependent post_migrate behavior still works.