Well, I got different results (so maybe it's version related). I tried it
on MySQL v5.7.16-log:
+----+------+
| id | v |
+----+------+
| 2 | two |
| 10 | one |
+----+------+
+----+------+
| id | v |
+----+------+
| 10 | one |
| 40 | two |
+----+------+
+----+-------+
| id | v |
+----+-------+
| 3 | three |
| 10 | one |
| 30 | two |
+----+-------+
-----Original Message-----
From: Simon Slavin
Sent: Tuesday, November 01, 2016 1:50 PM
To: SQLite mailing list
Subject: Re: [sqlite] Autoincrement sequence not updated by UPDATE
On 1 Nov 2016, at 11:44am, Andy Ling <andy.l...@s-a-m.com> wrote:
It remembers......
Ah, neat. Thanks for the testing. And the "show create table" command you
used makes it clear that the engine keeps a record for the table.
Apparently a single value for the table's primary key rather than a value
for each "INTEGER PRIMARY KEY AUTOINCREMENT" column.
I'd be interested in the equivalents for progresql and Oracle, if anyone is
set up to find out. Maybe we could work up a table like the one in
<https://www.sqlite.org/nulls.html>
Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
