On Dec 15, 2008, at 10:52 AM, Thomas Briggs wrote: >> Secondly, AUTOINCREMENT in SQLite only works on an INTEGER PRIMARY >> KEY, not on any other kind of primary key or on any non-primary-key >> field. BIGINT PRIMARY KEY is not an INTEGER PRIMARY KEY and so >> AUTOINCREMENT won't work on it. > > I think he understands that. :) His question is why. I think that > the answer is simply "convention", FWIW. > > That, unfortunately, leads directly to the follow-up question of > "can BIGINT PRIMARY KEY AUTOINCREMENT" be made to work the same as > INTEGER PRIMARY KEY AUTOINCREMENT". I believe the answer is yes, but > I wouldn't bet my life on it.
It might be possible to get BIGINT PRIMARY KEY AUTOINCREMENT to work like INTEGER PRIMARY KEY AUTOINCREMENT. Or perhaps it is not. That is unclear. Certainly it would be a rather substantial change - much, much larger than the little patch supplied on the ticket. My doubts about whether or not it will work derive from the fact that a BIGINT column can store strings and blobs in addition to integers. How do you AUTOINCREMENT a blob? > > > -T > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
