delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/query.py, branch pr/41

- Fixed a regression introduced by :ticket:`2818` where the EXISTS

2013-10-30T14:34:31+00:00

query being generated would produce a "columns being replaced"
warning for a statement with two same-named columns,
as the internal SELECT wouldn't have use_labels set.

An overhaul of expression handling for special symbols particularly

2013-10-23T21:44:52+00:00

with conjunctions, e.g.
``None`` :func:`.expression.null` :func:`.expression.true`
:func:`.expression.false`, including consistency in rendering NULL
in conjunctions, "short-circuiting" of :func:`.and_` and :func:`.or_`
expressions which contain boolean constants, and rendering of
boolean constants and expressions as compared to "1" or "0" for backends
that don't feature ``true``/``false`` constants. [ticket:2804]

- add an option to Bundle single_entity=True to allow for single

2013-10-07T16:53:04+00:00

entity returns without otherwise changing much [ticket:2824]

- merge ticket_1418 branch, [ticket:1418]

2013-10-07T00:29:08+00:00

- The system of loader options has been entirely rearchitected to build
upon a much more comprehensive base, the :class:`.Load` object.  This
base allows any common loader option like :func:`.joinedload`,
:func:`.defer`, etc. to be used in a "chained" style for the purpose
of specifying options down a path, such as ``joinedload("foo").subqueryload("bar")``.
The new system supersedes the usage of dot-separated path names,
multiple attributes within options, and the usage of ``_all()`` options.
-  Added a new load option :func:`.orm.load_only`.  This allows a series
of column names to be specified as loading "only" those attributes,
deferring the rest.

fix entity_zero resolution

2013-10-04T19:22:43+00:00

- A new construct :class:`.Bundle` is added, which allows for specification

2013-10-03T21:06:55+00:00

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

Fixed Query.exists() method for the case, when query doesn't have any filters applied.

2013-09-04T15:45:14+00:00

- "primary mapper entity" is now an attribute on Query,

2013-08-24T15:27:44+00:00

making _MapperEntity slightly less dependent on a particular parent
Query (in theory more shareable by multiple Query objects in different contexts)
- remove some comments that have been misunderstanding what _mapper_entities
does, or perhaps forgot to get removed
- simplify _mapper_entities

- also do delete, add seealsos, formatting, etc. [ticket:2798]

2013-08-18T19:15:38+00:00

- add better notes to query.update(), most notably how to deal with a joined table

2013-08-18T19:01:59+00:00

update, [ticket:2798]