diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-03-28 19:59:54 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-03-28 19:59:54 -0400 |
| commit | f258c224d7087ffc71d1b9b70f33235d86c6ed20 (patch) | |
| tree | d8bd5880ff7d8d7bb4b5c2ea0eb858c76d9a944e | |
| parent | ccc0c44c3a60fc4906e5e3b26cc6d2b7a69d33bf (diff) | |
| download | sqlalchemy-f258c224d7087ffc71d1b9b70f33235d86c6ed20.tar.gz | |
- fix mapper ref
- don't talk about "can't check for rows matched" here as we changed that in 0.9
| -rw-r--r-- | doc/build/changelog/changelog_08.rst | 3 | ||||
| -rw-r--r-- | doc/build/changelog/changelog_09.rst | 2 |
2 files changed, 1 insertions, 4 deletions
diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst index d6c4d4e53..0862463a7 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 aa61fbfc9..05e0f51b3 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 |