From ae3c57f492c5ade1afd8b010f7d9f2db740eb595 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 20 Dec 2013 10:26:09 -0500 Subject: - Fixed issue where a primary key column that has a Sequence on it, yet the column is not the "auto increment" column, either because it has a foreign key constraint or ``autoincrement=False`` set, would attempt to fire the Sequence on INSERT for backends that don't support sequences, when presented with an INSERT missing the primary key value. This would take place on non-sequence backends like SQLite, MySQL. [ticket:2896] --- doc/build/changelog/changelog_08.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc') diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst index 5b6a99f3e..08f8314c5 100644 --- a/doc/build/changelog/changelog_08.rst +++ b/doc/build/changelog/changelog_08.rst @@ -11,6 +11,19 @@ .. changelog:: :version: 0.8.5 + .. change:: + :tags: bug, sql + :versions: 0.9.0b2 + :tickets: 2896 + + Fixed issue where a primary key column that has a Sequence on it, + yet the column is not the "auto increment" column, either because + it has a foreign key constraint or ``autoincrement=False`` set, + would attempt to fire the Sequence on INSERT for backends that don't + support sequences, when presented with an INSERT missing the primary + key value. This would take place on non-sequence backends like + SQLite, MySQL. + .. change:: :tags: bug, sql :versions: 0.9.0b2 -- cgit v1.2.1