According to the SQLite documentation, indices that refer to tables must be dropped while doing the out-of-place table recreation. Foreign keys must likewise be temporarily disabled and then checked before re-enabling. This is the last major piece of migrations as far as I am currently aware.
According to the [SQLite documentation](https://www.sqlite.org/lang_altertable.html), indices that refer to tables must be dropped while doing the out-of-place table recreation. Foreign keys must likewise be temporarily disabled and then checked before re-enabling. This is the last major piece of migrations as far as I am currently aware.
Commit f0c59f36f0 adds consumer-facing support for foreign key migrations, though full integrity checks etc are not yet run.
Commit f0c59f36f040c73359b2747d4a7f09d91026aa95 adds consumer-facing support for foreign key migrations, though full integrity checks etc are not yet run.
kestrel
According to the SQLite documentation, indices that refer to tables must be dropped while doing the out-of-place table recreation. Foreign keys must likewise be temporarily disabled and then checked before re-enabling. This is the last major piece of migrations as far as I am currently aware.
Commit
f0c59f36f0adds consumer-facing support for foreign key migrations, though full integrity checks etc are not yet run.Full integrity checks are now run for indices, and in theory, foreign key support should simply 'work'. Testing is required, however.