summaryrefslogtreecommitdiff
path: root/examples/beaker_caching/model.py
Commit message (Collapse)AuthorAgeFilesLines
* - converted beaker demo to dogpile.cache, [ticket:2589]Mike Bayer2012-10-211-106/+0
|
* -whitespace bonanza, contdMike Bayer2012-07-281-2/+2
|
* - whitespace removal bonanzaMike Bayer2011-01-021-11/+11
|
* - The beaker_caching example has been reorgnizedMike Bayer2010-07-211-1/+3
| | | | | | | | such that the Session, cache manager, declarative_base are part of environment, and custom cache code is portable and now within "caching_query.py". This allows the example to be easier to "drop in" to existing projects.
* - The official name for the relation() function is nowMike Bayer2010-03-171-10/+10
| | | | | | relationship(), to eliminate confusion over the relational algebra term. relation() however will remain available in equal capacity for the foreseeable future. [ticket:1740]
* - Changed the beaker cache example a bit to have a separateMike Bayer2010-02-121-7/+8
| | | | | | | RelationCache option for lazyload caching. This object does a lookup among any number of potential attributes more efficiently by grouping several into a common structure. Both FromCache and RelationCache are simpler individually.
* add more examples, start basicMike Bayer2010-01-131-0/+3
|
* - cut down on a few hundred method callsMike Bayer2010-01-111-2/+2
|
* - merge() will not issue a needless merge of attributes if theMike Bayer2010-01-101-0/+100
given instance is the same instance which is already present. - merge() now also merges the "options" associated with a given state, i.e. those passed through query.options() which follow along with an instance, such as options to eagerly- or lazyily- load various attributes. This is essential for the construction of highly integrated caching schemes. This is a subtle behavioral change vs. 0.5. - A bug was fixed regarding the serialization of the "loader path" present on an instance's state, which is also necessary when combining the usage of merge() with serialized state and associated options that should be preserved. - The "query_cache" examples have been removed, and are replaced with a fully comprehensive approach that combines the usage of Beaker with SQLAlchemy. New query options are used to indicate the caching characteristics of a particular Query, which can also be invoked deep within an object graph when lazily loading related objects. See /examples/beaker_caching/README.