- fix mapper ref

- don't talk about "can't check for rows matched" here as we changed that in 0.9

diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst
index d6c4d4e53478badc12731cb57d497a706543fa30..0862463a7ace46fc7d856c44324d3a3e142b3b87 100644 (file)
--- 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 aa61fbfc93f198260d3204c9d1ffdc6dd76323e7..05e0f51b3ddb704330856a7d914945e366a1b235 100644 (file)
--- 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