On 6 Oct 2016, at 2:46pm, Jeff Archer <jeffarch...@gmail.com> wrote:
> Are there any performance or other considerations of the order of the > fields for an insert? No. Order of columns in the CREATE TABLE command matters. Order they're named in operations after that doesn't. When SQLite needs to fetch values from a table row, it has to start reading the row at the first column mentioned in CREATE TABLE, then go through it reading data until it has reached the last column it needs. Because of this it's best to put short, frequently-needed columns first in your CREATE TABLE command. Long columns, especially TEXT or BLOBs which may have lots of data in, should go at the end. Because you don't want SQLite to have to fetch all that data from storage just to get at the column after it. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
