]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9d3e220) | patch
don't create a history entry when an object in a backref has changed
authorMatt Chisholm <matt@theory.org>
Sat, 15 Jun 2013 16:15:29 +0000 (18:15 +0200)
committerMatt Chisholm <matt@theory.org>
Sat, 15 Jun 2013 16:15:29 +0000 (18:15 +0200)
commitd6c60cb2f3b1bf27f10aecf542fc0e3f3f903183
tree5256b6ce425d43b6f2ac3c6a5da41f0c1891a7a7tree | snapshot
parent9d3e2206363d819ad334d7893c700b861fdc5b57commit | diff
don't create a history entry when an object in a backref has changed

The code that determines whether an object in a relation has been added/removed does not take into account that that relation may be a backref. If the relation is a backref, then nothing on the current table is changing, and therefore no history entry should be created.
examples/versioning/history_meta.py diff | blob | blame | history
examples/versioning/test_versioning.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git