]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Set autoincrement to False; use sqlite_autoincrement in versioned_history
authorCarlos García Montoro <TrilceAC@gmail.com>
Mon, 9 Jan 2017 22:46:25 +0000 (17:46 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Mon, 9 Jan 2017 23:00:33 +0000 (18:00 -0500)
commitc703b9ce89483b6f44b97d1fbf56f8df8b14305a
tree847329031f1ec2be3f1ef97a6f9059bd29a13585
parente251f64d686ca62a338c53d40ca72bf7a3cc82cd
Set autoincrement to False; use sqlite_autoincrement in versioned_history

Ensure that the history table sets autoincrement=False, since these values
are copied in all cases; the flag will emit an error as of 1.1 if the
primary key is composite.   Additionally, use the sqlite_autoincrement flag
so that SQLite uses unique primary key identifiers for new rows even if
some rows have been deleted.

Fixes: #3872
Change-Id: I65912eb394b3b69d7f4e3c098f4f948b0a7a5374
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/93
doc/build/changelog/changelog_11.rst
examples/versioned_history/history_meta.py
examples/versioned_history/test_versioning.py