From f258c224d7087ffc71d1b9b70f33235d86c6ed20 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 28 Mar 2014 19:59:54 -0400 Subject: [PATCH] - fix mapper ref - don't talk about "can't check for rows matched" here as we changed that in 0.9 --- doc/build/changelog/changelog_08.rst | 3 --- doc/build/changelog/changelog_09.rst | 2 +- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst index d6c4d4e534..0862463a7a 100644 --- a/doc/build/changelog/changelog_08.rst +++ b/doc/build/changelog/changelog_08.rst @@ -19,9 +19,6 @@ Fixed ORM bug where changing the primary key of an object, then marking it for DELETE would fail to target the correct row for DELETE. - Note that we cannot currently check "number of rows matched" in general - for DELETE statements as we can't be sure that a self-referential - ON DELETE CASCADE has gotten there first. .. change:: :tags: feature, postgresql diff --git a/doc/build/changelog/changelog_09.rst b/doc/build/changelog/changelog_09.rst index aa61fbfc93..05e0f51b3d 100644 --- a/doc/build/changelog/changelog_09.rst +++ b/doc/build/changelog/changelog_09.rst @@ -19,7 +19,7 @@ :tags: feature, orm :tickets: 3007 - Added new parameter :paramref:`.mapper.confirm_deleted_rows`. Defaults + Added new parameter :paramref:`.orm.mapper.confirm_deleted_rows`. Defaults to True, indicates that a series of DELETE statements should confirm that the cursor rowcount matches the number of primary keys that should have matched; this behavior had been taken off in most cases -- 2.47.3