On 08.10.2012 22:12 CE(S)T, Richard Hipp wrote: > ALTER TABLE DROP COLUMN requires writing every row of the table.
Actually, I wouldn't care what the engine needs to do to get the job done. If it's documented that a certain command requires more time, it would be perfectly fine. SELECT queries also don't always return in a constant time, each of them requires different work to be done. So, to update my question: Why doesn't SQLite support DDL commands that internally need recreating the table or may not return in O(1) time? Of course, when the engine recreates the table, I'd expect it to maintain all foreign key references, if possible. That's probably even more work from the outside as a normal database user. (You know, the engine can trust the things it does itself (at least I hope so), but it doesn't necessarily trust the things a user does.) -- Yves Goergen - nospam.l...@unclassified.de - http://unclassified.de _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
