Matt Chisholm d6c60cb2f3 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.

2013-06-15 18:15:29 +02:00

..

adjacency_list

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

association

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

custom_attributes

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

dogpile_caching

Merge branch 'master' into rel_0_9

2013-05-28 01:22:32 -04:00

dynamic_dict

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

elementtree

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

generic_associations

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

graphs

whack more long lines in very old docstrings

2013-02-02 18:54:54 -05:00

inheritance

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

large_collection

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

nested_sets

modernize some more examples

2013-04-27 17:21:31 -04:00

postgis

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

sharding

-whitespace bonanza, contd

2012-07-28 17:05:50 -04:00

versioning

don't create a history entry when an object in a backref has changed

2013-06-15 18:15:29 +02:00

vertical

- the raw 2to3 run

2013-04-27 19:53:57 -04:00

__init__.py

Added in Examples into the test suite so they get exercised regularly. Cleaned up some deprecation warnings in the examples.

2009-07-27 02:12:15 +00:00