Optimize Alter Table Speed in case of sqlite3

Issue #237 open
Christopher Kramer created an issue

Originally reported on Google Code with ID 237

Currently, the ALTER TABLE workaround copies the data of the table twice, first in a
temporary table and then in the new target table.
As SQLite3 can rename tables, it would be possible to rename the temporary table into
the final table name without the need to copy the data again.
So altering a big table would only need about half the time it currently needs.

Reported by crazy4chrissi on 2013-12-25 13:13:30

Comments (1)

  1. Log in to comment