From 3feea4503ff211cdd1f6046b4b8ae16cf0dd08a3 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Thu, 31 Aug 2017 15:46:53 -0400 Subject: Consider merge key with (None, ) as non-persistent Fixed bug in :meth:`.Session.merge` where objects in a collection that had the primary key attribute set to ``None`` for a key that is typically autoincrementing would be considered to be a database-persisted key for part of the internal deduplication process, causing only one object to actually be inserted in the database. Change-Id: I0a6e00043be0b2979cda33740e1be3b430ecf8c7 Fixes: #4056 (cherry picked from commit 5243341ed886e10a0d3f7fef8ae3d071e0ffdcf0) --- doc/build/changelog/unreleased_11/4056.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/build/changelog/unreleased_11/4056.rst (limited to 'doc') diff --git a/doc/build/changelog/unreleased_11/4056.rst b/doc/build/changelog/unreleased_11/4056.rst new file mode 100644 index 000000000..b8e02a05e --- /dev/null +++ b/doc/build/changelog/unreleased_11/4056.rst @@ -0,0 +1,10 @@ +.. change:: + :tags: bug, orm + :tickets: 4056 + :versions: 1.2.0b3 + + Fixed bug in :meth:`.Session.merge` where objects in a collection that had + the primary key attribute set to ``None`` for a key that is typically + autoincrementing would be considered to be a database-persisted key for + part of the internal deduplication process, causing only one object to + actually be inserted in the database. -- cgit v1.2.1