On 17/06/2009 6:17 AM, Hoover, Jeffrey wrote: > One other note, if you have a primary key whose value is continually > increasing your pk index can become imbalanced and therefore > inefficient.
A B-tree becomes imbalanced? How so? http://www.sqlite.org/fileformat.html#btree_structures says: "The tree is always of uniform height, meaning the number of intermediate levels between each leaf node page and the root page is the same." Do you have any evidence to the contrary? > You may be able to get around this by using INTEGER > PRIMARY KEY (or INTEGER PRIMARY KEY AUTOINCREMENT). So with autoincrement SQLite3 generates the "continually increasing" pk values instead of the app doing it, and that solves the alleged problem? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
