mirror of
https://github.com/silverstripe/silverstripe-sqlite3
synced 2024-10-22 17:05:37 +02:00
62ef14f711
Transactions that used more than one level would cause errors if there were consecutive calls to start a transaction - because each query executed would clear the flag indicating that a transaction was already in progress. The comment for the logic to reset the nesting level on a query was indicating that DDL (data definition language) would not work within a transaction. This is untrue, and the module itself uses a transaction to alter table or field names. So this function has been converted to a no-op, deprecated to be removed in version 3 of this module. It is also no longer called upon each query. There have been some maintenance tidyups around this area also by abstracting the nested transaction flag manipulations into protected functions. |
||
|---|---|---|
| .. | ||
| SQLite3Connector.php | ||
| SQLite3Database.php | ||
| SQLite3Query.php | ||
| SQLite3QueryBuilder.php | ||
| SQLite3SchemaManager.php | ||
| SQLiteDatabaseConfigurationHelper.php | ||