delta/python-packages/sqlalchemy.git/examples/versioning, branch pr/12

Forgot final check that a delete in a backref also doesn't create a new version

2013-06-17T21:30:07+00:00

follow up to https://bitbucket.org/zzzeek/sqlalchemy/pull-request/2

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

2013-06-15T16:15:29+00:00

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.

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls

modernize some more examples

2013-04-27T21:21:31+00:00

whack more long lines in very old docstrings

2013-02-02T23:54:54+00:00

-whitespace bonanza, contd

2012-07-28T21:05:50+00:00

trailing whitespace bonanza

2012-07-28T19:50:05+00:00

- [feature] Simplified the versioning example

2012-01-23T00:03:06+00:00

a bit to use a declarative mixin as well
as an event listener, instead of a metaclass +
SessionExtension.  [ticket:2313]

- Fixed bug in history_meta.py example where

2011-10-17T17:26:26+00:00

the "unique" flag was not removed from a
single-table-inheritance subclass which
generates columns to put up onto the base.

- Repaired the examples/versioning test runner

2011-06-16T16:09:45+00:00

to not rely upon SQLAlchemy test libs,
nosetests must be run from within
examples/versioning to get around setup.cfg
breaking it.

- Tweak to examples/versioning to pick the
correct foreign key in a multi-level
inheritance situation.