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

- 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)

- do the trailing comma logic of tuple repr() exactly

2016-02-17T20:21:00+00:00

- All string formatting of bound parameter sets and result rows for

2016-02-17T18:31:29+00:00

logging, exception, and  ``repr()`` purposes now truncate very large
scalar values within each collection, including an
"N characters truncated"
notation, similar to how the display for large multiple-parameter sets
are themselves truncated.
fixes #2837

- use same colname as the alias we give to the PG function

2016-02-16T15:05:58+00:00

here, fixes #3652

- CTE functionality has been expanded to support all DML, allowing

2016-02-11T17:27:28+00:00

INSERT, UPDATE, and DELETE statements to both specify their own
WITH clause, as well as for these statements themselves to be
CTE expressions when they include a RETURNING clause.
fixes #2551

- A refinement to the logic which adds columns to the resulting SQL when

2016-02-09T22:49:38+00:00

:meth:`.Query.distinct` is combined with :meth:`.Query.order_by` such
that columns which are already present will not be added
a second time, even if they are labeled with a different name.
Regardless of this change, the extra columns added to the SQL have
never been returned in the final result, so this change only impacts
the string form of the statement as well as its behavior when used in
a Core execution context.   Additionally, columns are no longer added
when the DISTINCT ON format is used, provided the query is not
wrapped inside a subquery due to joined eager loading.
fixes #3641

- oracle requires GLOBAL here

2016-02-04T00:34:29+00:00

- add literal_binds for delete() statements in addition to insert()/update()

2016-02-03T16:07:44+00:00

- move tests to CRUDTest
- changelog, fixes #3643