On Fri, Aug 04, 2017 at 10:09:04PM +0200, Sylvain Pointeau wrote: > On Fri, Aug 4, 2017 at 10:01 PM, Nico Williams <[email protected]> > wrote: > > The main issue is that you can't tell when a transaction has begun or > > ended, so you can't tell when curr_val() should raise an error. You can > > only tell that next_val() has been called on this connection, and that's > > not the same semantics as H2's. > > actually the temp table is better in case of rollback.
Right. > however normally it should be executed under an autonomous transaction, > a rollback should not affect the sequence. Correct. > > I would just not bother with curr_val() for now. > > I need it, but the current implementation should be enough. OK. > => I would really really like if a real implementation of the sequence > could be done in sqlite, behaving like oracle. > (very fast, reliable etc) > > Thanks for all your help! You're welcome. Thanks for posting this on github. Make sure there's a license, preferably a nice and friendly one such as a BSD license, or else put it in the public domain like SQLite3 is -- but it's your code, so you do what you like with it. Cheers, Nico -- _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
