mirror of
https://github.com/silverstripe/silverstripe-sqlite3
synced 2024-10-22 17:05:37 +02:00
5eacbe7842
It is not uncommon for an index to be defined as e.g. 'fulltext' which SQLite3 does not support without a module to create a virtual table (rather than an index on an existing one). The code already in place sees that definitions be updated to 'index' on the fly during creation and later inspection (indexList) - which causes issue when comparing existing table definitions to what SilverStripe expects by DataObject configuration. This discrepency leads to tables constantly being marked to update, although effectively nothing actually changes. We can save these CPU cycles and a bit of head scratching by converting to a supported index type. |
||
|---|---|---|
| .. | ||
| SQLite3Connector.php | ||
| SQLite3Database.php | ||
| SQLite3Query.php | ||
| SQLite3QueryBuilder.php | ||
| SQLite3SchemaManager.php | ||
| SQLiteDatabaseConfigurationHelper.php | ||