On Tue, Mar 8, 2011 at 9:36 AM, Simon Slavin <slav...@bigfraud.org> wrote: > Yes. Is there any reason why you don't use your own sequences instead of > relying on SQLite's functions ? You could simply use something like > max(id)+1 .
Without speaking for the OP, sequences are state that changes when read, thus your suggestion won't do. There has to be an insert/update/delete in order to implement nextval. This requires either generating VDBE code or a function that re-enters SQLite3 to perform the modification. Even better would be to avoid sequences altogether. But I'm sure they are useful, because expressive. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
