delta/python-packages/sqlalchemy.git/test/sql, branch pr/252

- 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

- move out unconsumed names tests from test_compiler out to test_insert, test_update

2016-03-03T01:24:49+00:00

- establish consistent names between existing unconsumed names tests and new ones
added per ref #3666

Add test for inserting multiple values

2016-03-02T19:43:09+00:00

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

- 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

- Fixed bug in :func:`.expression.text` construct where a double-colon

2016-02-09T23:05:40+00:00

expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644

- 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

fix passing literal_binds flag through for update and insert

2016-02-02T23:40:07+00:00

- add changelog and migration notes for new Enum features,

2016-02-02T20:04:46+00:00

fixes #3095, #3292
- reorganize enum constructor to again work with the MySQL
ENUM type
- add a new create_constraint flag to Enum to complement that of
Boolean
- reinstate the CHECK constraint tests for enum, these already
fail /skip against the MySQL backend
- simplify lookup rules in Enum, have them apply to all varieties
of Enum equally