On Wed, Dec 9, 2015 at 7:14 AM, Clemens Ladisch <clemens at ladisch.de> wrote:
> David Baird wrote: > > # INSERT INTO "StringIntern" VALUES(5,'c'); <-- undesired behavior > > # INSERT INTO "StringIntern" VALUES(3,'c'); <-- desired behavior > > Works for me. Are you sure you actually executed this actual code? > > <http://www.sqlite.org/autoinc.html> guarantees that a newly inserted > row uses the next available rowid value, if you have an INTEGER PRIMARY > KEY column. You might get the undesired behaviour only with an INTEGER > PRIMARY KEY AUTOINCREMENT column. > Just tried two different versions: SQLite version 3.8.2 2013-12-06 14:53:30 (that is bundled with my OS): has the undesired behavior SQLite version 3.9.2 2015-11-02 18:31:45 (that I built myself): has desired behavior Looks like it's fixed, as long as I stick to new versions. *cross fingers* Thanks!
