delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql, branch pr/83

- Restored the import for :class:`.Function` to the ``sqlalchemy.sql.expression``

2014-04-06T01:05:29+00:00

import namespace, which was removed at the beginning of 0.9.

escape backslash

2014-04-02T22:14:10+00:00

- 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

- back off the callcounts a bit for the boolean fix

2014-04-01T22:29:54+00:00

- rewrite callcounts for select()

- 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

- Added new flag :paramref:`.expression.between.symmetric`, when set to True

2014-03-31T01:20:20+00:00

renders "BETWEEN SYMMETRIC".  Also added a new negation operator
"notbetween_op", which now allows an expression like ``~col.between(x, y)``
to render as "col NOT BETWEEN x AND y", rather than a parentheiszed NOT
string.  fixes #2990

- add further coverage for join_condition to make sure we get this case where

2014-03-28T20:41:08+00:00

there are multiple, equivalent foreign keys

- fix set syntax supposed to be dict

2014-03-28T20:36:11+00:00

- fix py3k bug re: dictionary values(), fixes #3005

2014-03-28T15:02:34+00:00

- Improved the check for "how to join from A to B" such that when

2014-03-27T23:43:15+00:00

a table has multiple, composite foreign keys targeting a parent table,
the :paramref:`.relationship.foreign_keys` argument will be properly
interpreted in order to resolve the ambiguity; previously this condition
would raise that there were multiple FK paths when in fact the
foreign_keys argument should be establishing which one is expected.
fixes #2965