Motivation
#2980 added support for running migrations atomically inside of a transaction, but only enabled it for PostgreSQL. SQLite can also run DDL statements inside of transactions and roll them back, so atomic migrations should be used for it as well by default.
Proposed Solutions
Extend the check for PostgreSQL to check for SQLite as well.
Additional Information
The PR added a way to force using a transaction using fn use_transaction(&self) -> Option<bool> { Some(true) } but it's boilerplate-y.
Motivation
#2980 added support for running migrations atomically inside of a transaction, but only enabled it for PostgreSQL. SQLite can also run DDL statements inside of transactions and roll them back, so atomic migrations should be used for it as well by default.
Proposed Solutions
Extend the check for PostgreSQL to check for SQLite as well.
Additional Information
The PR added a way to force using a transaction using
fn use_transaction(&self) -> Option<bool> { Some(true) }but it's boilerplate-y.