delta/python-packages/sqlalchemy.git/examples, branch pr/28 github.com: zzzeek/sqlalchemy.git - reorganize docs so expression, schema are broken out into subfiles, they're too big 2013-08-18T22:01:27+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-08-18T22:01:27+00:00 0c19c1c66f3a115f5ce710de571552d68fac6358 - fix the targeting of module names moved around by using custom handlers for "Bases", etc. 
- fix the targeting of module names moved around by using custom handlers for "Bases", etc.
- changelog 2013-08-17T04:20:46+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-08-17T04:20:46+00:00 d1028646099c408c66615fe2ab79d7713ef41e64 - clean up these tests to not use globals so much, close out the session 
- 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 Patrick R. Schmid prschmid@act.md 2013-07-31T21:12:40+00:00 4e0a03fabdc249cbaa5ddd7abaebb1cd19eed411 






modernize this a bit
2013-07-27T23:12:40+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

937c098d5a9b11f2707fc7bf57408cd98dae5c4e












- Improved the examples in ``examples/generic_associations``, including
2013-07-20T02:56:34+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

af61551a112b5cedcaf56470101b8a4f8523573d

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.





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

Matt Chisholm
matt@theory.org

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

f499b7b88397c9aa5b858aba62712bcddaea417e

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





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

Matt Chisholm
matt@theory.org

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

d6c60cb2f3b1bf27f10aecf542fc0e3f3f903183

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 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.







Merge branch 'master' into rel_0_9
2013-05-28T05:22:32+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-05-28T05:22:32+00:00

9fc6201f0c039631de436d38d7b162f56f9b08dd












Fixed a small bug in the dogpile example where the generation
2013-05-28T05:22:10+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-05-28T05:22:10+00:00

94096593ca92e105b8f716ff89b78856595d95c8

of SQL cache keys wasn't applying deduping labels to the
statement the same way :class:`.Query` normally does.





of SQL cache keys wasn't applying deduping labels to the
statement the same way :class:`.Query` normally does.







- the raw 2to3 run
2013-04-27T23:53:57+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

4b614b9b35cd2baddb7ca67c04bee5d70ec6a172

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





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