Re: [sqlite] Is this behavior expected?

ay to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Baruch Burstein >Sent: Sunday, 24 September, 2017 05:46 >To: General Discussion of SQLite Database >Subject:

Re: [sqlite] Is this behavior expected?

Baruch Burstein wrote: > sqlite> select last_insert_rowid(); > 2 > sqlite> rollback; > sqlite> select last_insert_rowid(); > 2 > > In other words, the rollback doesn't roll back the rowid. says: | For the purposes of this routine, an INSERT is

Re: [sqlite] Is this behavior expected?

Hi, On Sun, Sep 24, 2017 at 7:46 AM, Baruch Burstein wrote: > SQLite version 3.20.1 2017-08-24 16:21:36 > sqlite> create table T(C); > sqlite> insert into T values("test 1"); > sqlite> select last_insert_rowid(); > 1 > sqlite> begin; > sqlite> insert into T values("test

[sqlite] Is this behavior expected?

SQLite version 3.20.1 2017-08-24 16:21:36 sqlite> create table T(C); sqlite> insert into T values("test 1"); sqlite> select last_insert_rowid(); 1 sqlite> begin; sqlite> insert into T values("test 2"); sqlite> select last_insert_rowid(); 2 sqlite> rollback; sqlite> select last_insert_rowid(); 2