[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2013-10-03 21:08:13
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/97fec60b49a1/ Changeset: 97fec60b49a1 Branch: ticket_2824 User: zzzeek Date: 2013-10-03 20:58:08 Summary: - rework how Query gets at the Bundle in composite, as we need __clause_element__() to keep returning a real ClauseElement Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a83378b64005/ Changeset: a83378b64005 Branch: master User: zzzeek Date: 2013-10-03 23:06:55 Summary: - A new construct :class:`.Bundle` is added, which allows for specification of groups of column expressions to a :class:`.Query` construct. The group of columns are returned as a single tuple by default. The behavior of :class:`.Bundle` can be overridden however to provide any sort of result processing to the returned row. One example included is :attr:`.Composite.Comparator.bundle`, which applies a bundled form of a "composite" mapped attribute. [ticket:2824] - The :func:`.composite` construct now maintains the return object when used in a column-oriented :class:`.Query`, rather than expanding out into individual columns. This makes use of the new :class:`.Bundle` feature internally. This behavior is backwards incompatible; to select from a composite column which will expand out, use ``MyClass.some_composite.clauses``. Affected #: 11 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |