On Thu, Jul 23, 2009 at 06:22:53PM +0100, Simon Slavin scratched on the wall: > > On 23 Jul 2009, at 4:56pm, Rich Shepard wrote: > > > Using rowid for anything is not a good idea. There's no guarantee > > that the > > column values associated with each rowid are static. It's much > > better to > > ignore the rowid and use either a natural primary key or a defined > > one. > > Agreed. And note that if you have a column which is an integer that > has doesn't allow duplicates,
The column has to very specifically be defined "INTEGER PRIMARY KEY". "INT UNIQUE" won't cover it. http://sqlite.org/lang_createtable.html#rowid -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users