delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql/compiler.py, branch pr/238

- 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

- 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

fix passing literal_binds flag through for update and insert

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

- happy new year

2016-01-29T16:20:22+00:00

- The workaround for right-nested joins on SQLite, where they are rewritten

2016-01-26T21:09:23+00:00

as subqueries in order to work around SQLite's lack of support for this
syntax, is lifted when SQLite version 3.7.16 or greater is detected.
fixes #3634
- The workaround for SQLite's unexpected delivery of column names as
``tablename.columnname`` for some kinds of queries is now disabled
when SQLite version 3.10.0 or greater is detected.
fixes #3633

- calling str() on a core sql construct has been made more "friendly",

2016-01-19T21:47:16+00:00

when the construct contains non-standard sql elements such as
returning, array index operations, or dialect-specific or custom
datatypes.  a string is now returned in these cases rendering an
approximation of the construct (typically the postgresql-style
version of it) rather than raising an error. fixes #3631
- add within_group to top-level imports
- add eq_ignore_whitespace to sqlalchemy.testing imports

- A deep improvement to the recently added :meth:`.TextClause.columns`

2016-01-14T23:06:26+00:00

method, and its interaction with result-row processing, now allows
the columns passed to the method to be positionally matched with the
result columns in the statement, rather than matching on name alone.
The advantage to this includes that when linking a textual SQL statement
to an ORM or Core table model, no system of labeling or de-duping of
common column names needs to occur, which also means there's no need
to worry about how label names match to ORM columns and so-forth.  In
addition, the :class:`.ResultProxy` has been further enhanced to
map column and string keys to a row with greater precision in some
cases.  fixes #3501
- reorganize the initialization of ResultMetaData for readability
and complexity; use the name "cursor_description", define the
task of "merging" cursor_description with compiled column information
as its own function, and also define "name extraction" as a separate task.
- fully change the name we use in the "ambiguous column" error to be the
actual name that was ambiguous, modify the C ext also

- reorganize schema_translate_map to be succinct and gain the performance

2016-01-11T21:44:28+00:00

back by using an attrgetter for the default case

- Multi-tenancy schema translation for :class:`.Table` objects is added.

2016-01-09T03:12:25+00:00

This supports the use case of an application that uses the same set of
:class:`.Table` objects in many schemas, such as schema-per-user.
A new execution option
:paramref:`.Connection.execution_options.schema_translate_map` is
added. fixes #2685
- latest tox doesn't like the {posargs} in the profile rerunner