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

- Added :meth:`.Select.lateral` and related constructs to allow

2016-03-29T21:56:02+00:00

for the SQL standard LATERAL keyword, currently only supported
by Postgresql.  fixes #2857

- Added support for rendering "FULL OUTER JOIN" to both Core and ORM.

2016-03-28T15:50:09+00:00

Pull request courtesy Stefan Urbanek.  fixes #1957

- Fixed bug where the negation of an EXISTS expression would not

2016-03-21T14:57:40+00:00

be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682

Raise exception when we have multiple values with an unknown column. Fixes #3666.

2016-03-02T19:16:14+00:00

- unfortunately calling upon "_label" here makes it unclear if

2016-02-26T16:27:49+00:00

we're trying to hit columns without names yet and such, to suit the bug
right now just make it specific to FunctionElement

(cherry picked from commit 785224a92f39bd5bdd05bbc66f4dd79736abded5)

- Anonymous labeling is applied to a :attr:`.func` construct that is

2016-02-26T05:20:39+00:00

passed to :func:`.column_property`, so that if the same attribute
is referred to as a column expression twice the names are de-duped,
thus avoiding "ambiguous column" errors.   Previously, the
``.label(None)`` would need to be applied in order for the name
to be de-anonymized.
fixes #3663

- additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f

2016-02-22T03:49:29+00:00

for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.

(cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e)

- reworked the way the "select_wraps_for" expression is

2016-02-21T01:22:38+00:00

handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement.  The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe.  fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.

- further edit the unnest() example to suit PG's esoteric requirements

2016-02-18T16:33:19+00:00

exactly

- handle parameter sets that aren't correctly formed, so that

2016-02-17T21:53:01+00:00

for example an exception object made within a test suite can
still repr (error seen in Keystone)