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

- add a new sphinx extension "viewsource". takes advantage of part of the viewcode extension

2013-11-10T00:42:01+00:00

to allow ad-hoc display of the source of any file, as well as a "directory listing" structure.
- reorganize examples/ to take advantage of new extension.  in particular, keep moving all
the descriptive text for files etc. into module docstrings, taking more advantage of
self-documentation.

- add proof of concept for versioning, [ticket:2861]

2013-11-08T23:19:41+00:00

- Fixed bug which prevented history_meta recipe from working with

2013-11-08T01:35:24+00:00

joined inheritance schemes more than one level deep.
- don't need to use _lib.py here anymore now that these features are in
sqlalchemy.testing

- reorganize docs so expression, schema are broken out into subfiles, they're too big

2013-08-18T22:01:27+00:00

- fix the targeting of module names moved around by using custom handlers for "Bases", etc.

- changelog

2013-08-17T04:20:46+00:00

- clean up these tests to not use globals so much, close out the session

Made primary_key autoincrement=False in versioning example.

2013-07-31T21:12:40+00:00

modernize this a bit

2013-07-27T23:12:40+00:00

- Improved the examples in ``examples/generic_associations``, including

2013-07-20T02:56:34+00:00

that ``discriminator_on_association.py`` makes use of single table
inheritance do the work with the "discriminator".  Also
added a true "generic foreign key" example, which works similarly
to other popular frameworks in that it uses an open-ended integer
to point to any other table, foregoing traditional referential
integrity.  While we don't recommend this pattern, information wants
to be free.  Also in 0.8.3.

- Added a convenience class decorator :func:`.as_declarative`, is
a wrapper for :func:`.declarative_base` which allows an existing base
class to be applied using a nifty class-decorated approach.  Also
in 0.8.3.

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.