Ensure that `background migrations` do not use transactions
What does this MR do and why?
Since we might be using database tracking tables it is not desired to schedule them in transaction, as some migrations might be scheduled before the transaction commits.
This is our general practice established to use disable_ddl_transaction!
in majority of those migrations. This ensures that.
Subset of:
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Kamil Trzciński