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

- 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

- Initial implementation of support for PEP-435 enumerated types

2016-02-02T19:21:54+00:00

within the Enum type.

- Fixed issue where inadvertent use of the Python ``contains``

2016-02-02T15:20:54+00:00

override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type.  Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642

- rework ColumnCollection to no longer persist "all_col_set"; we don't

2016-01-26T21:41:26+00:00

need this collection except in the extend/update uses where we
create it ad-hoc.  simplifies pickling.  Compatibility with 1.0
should be OK as ColumnColleciton uses __getstate__ in any case
and the __setstate__ contract hasn't changed.
- Fixed bug in :class:`.Table` metadata construct which appeared
around the 0.9 series where adding columns to a :class:`.Table`
that was unpickled would fail to correctly establish the
:class:`.Column` within the 'c' collection, leading to issues in
areas such as ORM configuration.   This could impact use cases such
as ``extend_existing`` and others.  fixes #3632

- 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

- native unicode expectations are too difficult to maintain

2016-01-23T19:30:30+00:00

w/ the number of drivers /DBURIs /  python versions

- add a forwards-test here as well

2016-01-21T20:32:53+00:00

- documenation updates to clarify specific SQLite versions

2016-01-21T20:21:33+00:00

that have problems with right-nested joins and UNION column keys;
references #3633 references #3634.   backport from 1.1 to 0.9
announcing 1.1 as where these behaviors will be retired based
on version-specific checks
- fix test_resultset so that it passes when SQLite 3.10.0 is
present, references #3633