http://sqlite.org/faq.html#q1
CURRENTLY: "(If the largest possible integer key, 9223372036854775807, then an unused key value is chosen at random.)" SUGGESTED FIX: " (If the largest possible integer key 9223372036854775807 is in use, then an unused key value is chosen at random.)" http://www.sqlite.org/autoinc.html CURRENTLY: "If the largest ROWID is equal to the largest possible integer (9223372036854775807) then the database engine starts picking positive candidate ROWIDs at random until it finds one that is not previously used." SUGGESTED FIX: "If the largest ROWID in use is equal to the largest possible integer (9223372036854775807) then the database engine starts picking positive candidate ROWIDs at random until it finds one that is not previously used." -- -- -- --Ô¿Ô-- K e V i N On Thu, Dec 12, 2013 at 9:11 AM, Richard Hipp <[email protected]> wrote: > Thanks. http://www.sqlite.org/docsrc/info/200941601a > > > On Wed, Dec 11, 2013 at 1:23 PM, Jeff Widman <[email protected]> wrote: > > > https://www.sqlite.org/queryplanner.html > > > > Current: *Then in general the cost of doing the query proportional to > > (K+1)*logN.* > > > > Suggested fix: *Then in general the cost of doing the query is > proportional > > to (K+1)*logN.* > > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
