Hi all, I've recently been looking into the implementation of sqlite3. I've added some prints to instrument various parts of the implementation in order to get a better picture of how things work.
I've noticed some strange behaviour when performing ALTER TABLE ADD COLUMN queries. It appears that sqlite3AddColumn (in build.c) is called for all existing columns in the table first, and only then for the new column. I would have expected that sqlite3AddColumn would only be called once, for the new column. This behaviour has performance implications, especially with tables which have a large number of columns. Is this expected behaviour? If so, why? If not, is it a bug? Thanks s1341 _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
