| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
| |
SQL expressions to be pickleable [ticket:735]
- small adjustment to mapper class.__init__ to allow for Py2.6 object.__init__()
behavior
|
| | |
|
| | |
|
| |
|
|
| |
- moved shard example/unittest over to sessionmaker
|
| |
|
|
| |
style queries
|
| |
|
|
|
|
| |
for EXT_CONTINUE.
Repointed docs and examples to EXT_CONTINUE
|
| |
|
|
| |
- disabled PG schema test for now (want to see the buildbot succeed)
|
| |
|
|
| |
maintenance branch in branches/rel_0_3.
|
| |
|
|
|
| |
- Deprecated BoundMetaData- use MetaData instead
- Removed DMD and BMD from documentation
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- changed polymorph example to use a single set of outerjoins
|
| | |
|
| | |
|
| |
|
|
| |
Rails' polymorphic associaiton functionality
|
| | |
|
| |
|
|
|
|
|
|
|
| |
will add the given mapper/class or ColumnElement to the query at compile
time, and apply them to the instances method. the user is responsible
for constructing reasonable join conditions (otherwise you can get
full cartesian products). result set is the list of tuples, non-uniqued.
- fixed multi-mapper instances() to pad out shorter results with None so
zip() gets everything
|
| |
|
|
|
| |
cleanup/completion of keyword arg documentation for create_engine(), mapper(), and
relation()
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
that the class of object attached to a parent object is appropriate
(i.e. if A.items stores B objects, raise an error if a C is appended to A.items)
- new extension sqlalchemy.ext.associationproxy, provides transparent "association object"
mappings. new example examples/association/proxied_association.py illustrates.
- some example cleanup
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- fixed table comparison example in metadata.txt
- docstrings all over the place
- renamed mapper _getattrbycolumn/_setattrbycolumn to get_attr_by_column,set_attr_by_column
- removed frommapper parameter from populate_instance(). the two operations can be performed separately
- fix to examples/adjacencytree/byroot_tree.py to fire off lazy loaders upon load, to reduce query calling
- added get(), get_by(), load() to MapperExtension
- re-implemented ExtensionOption (called by extension() function)
- redid _ExtensionCarrier to function dynamically based on __getattribute__
- added logging to attributes package, indicating the execution of a lazy callable
- going to close [ticket:329]
|
| | |
|
| |
|
|
|
| |
keyword argument to relation(). the old way still works but is
deprecated [ticket:212]
|
| |
|
|
|
|
|
|
| |
SelectionContext object to track state during the operation.
SLIGHT API BREAKAGE: the append_result() and populate_instances()
methods on MapperExtension have a slightly different method signature
now as a result of the change; hoping that these methods are not
in widespread use as of yet.
|
| |
|
|
|
|
|
|
|
|
| |
part of a "delete-orphan" cascade, for certain conditions where the
parent isnt available to cascade from.
- it is now invalid to declare a self-referential relationship with
"delete-orphan" (as the abovementioned check would make them impossible
to save)
- improved the check for objects being part of a session when the
unit of work seeks to flush() them as part of a relationship..
|
| | |
|
| |
|
|
| |
they will compile their internal state when first used in a query or flush operation (or their props or 'c'/'columns' attributes are used). includes various cleanups and fixes in support of the change, including some unit test changes, additional unit tests.
|
| |
|
|
| |
fixes to entity_name propigation
|
| | |
|
| |
|
|
| |
well as throughout the call-chain for those. lazy loader honors the "session" of the parent object, + added simple unit test
|
| | |
|
| | |
|
| |
|
|
| |
automatically configure themselves for this type of storage
|
| |
|
|
| |
columns of an underlying table
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
the case of
inheritance. relations now create priamry/secondary joins against that lead table. if you want to create it against
an inherited table, use explicit join conditions.
added 'correlate' argument to CompoundSelect to get polymorph example working again.
|
| |
|
|
| |
send keyword arguments that will be placed on the relation
|
| |
|
|
| |
mapper; even though this is not usually needed, it allows certain exotic combinations of mapper setups to work (i.e. the one in the polymorph example)
|
| |
|
|
|
| |
fixes to relation to enable it to locate "direction" more consistently with inheritance relationships
more tweaks to parenthesizing subqueries, unions, etc.
|
| |
|
|
| |
changed unit tests/examples to not do it
|