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

- reverse order of columns in sample CTEs as this is a UNION and the cols need to line up

2014-04-02T22:11:11+00:00

- alter this in the unit tests as well as these queries were just copied from the tests
- remove the included_parts.join(parts) from the core CTE doc (also just copied from the
test, where we want to make sure joins don't get screwed up with the CTE) as it doesn't
contribute to the query itself
fixes #3014

- Fixes to the newly enhanced boolean coercion in :ticket:`2804` where

2014-04-01T17:03:52+00:00

the new rules for "where" and "having" woudn't take effect for the
"whereclause" and "having" kw arguments of the :func:`.select` construct,
which is also what :class:`.Query` uses so wasn't working in the
ORM either. fixes #3013 re: #2804

- Fixed regression from 0.8.3 as a result of :ticket:`2818`

2014-03-22T23:55:00+00:00

where :meth:`.Query.exists` wouldn't work on a query that only
had a :meth:`.Query.select_from` entry but no other entities.
re: #2818 fixes #2995

- Improved an error message which would occur if a query() were made

2014-03-17T20:25:51+00:00

against a non-selectable, such as a :func:`.literal_column`, and then
an attempt was made to use :meth:`.Query.join` such that the "left"
side would be determined as ``None`` and then fail.  This condition
is now detected explicitly.

- correct this to make the intention clear

2014-03-14T00:14:23+00:00

- extensive cross-linking of relationship options with their documentation sections

2014-02-16T19:28:56+00:00

- convert all paramter references in relationship documentation to :paramref:

- Fixed bug where :meth:`.Query.get` would fail to consistently

2014-02-10T21:33:48+00:00

raise the :class:`.InvalidRequestError` that invokes when called
on a query with existing criterion, when the given identity is
already present in the identity map. [ticket:2951]

- Fixed bug in new :class:`.TextAsFrom` construct where :class:`.Column`-

2014-02-02T16:06:08+00:00

oriented row lookups were not matching up to the ad-hoc :class:`.ColumnClause`
objects that :class:`.TextAsFrom` generates, thereby making it not
usable as a target in :meth:`.Query.from_statement`.  Also fixed
:meth:`.Query.from_statement` mechanics to not mistake a :class:`.TextAsFrom`
for a :class:`.Select` construct.  This bug is also an 0.9 regression
as the :meth:`.Text.columns` method is called to accommodate the
:paramref:`.text.typemap` argument. [ticket:2932]

- remove this leftover commented pdb

2014-01-23T19:50:23+00:00

- Fixed an 0.9 regression where the automatic aliasing applied by

2014-01-23T19:49:04+00:00

:class:`.Query` and in other situations where selects or joins
were aliased (such as joined table inheritance) could fail if a
user-defined :class:`.Column` subclass were used in the expression.
In this case, the subclass would fail to propagate ORM-specific
"annotations" along needed by the adaptation.  The "expression
annotations" system has been corrected to account for this case.
[ticket:2918]