delta/python-packages/sqlalchemy.git/test/dialect/mysql/test_reflection.py, branch pr/220

- fix changelog for #3602

2015-12-08T18:50:25+00:00

- add version switch for backend fsp test

(cherry picked from commit 67b22cee3ab2c17b61100f1ccd69081082c0f074)

- make this DROP conditional, attempting to isolate why jenkins has

2015-12-08T15:40:45+00:00

an issue with just one test

- Fixed bug in MySQL reflection where the "fractional sections portion"

2015-12-07T22:24:09+00:00

of the :class:`.mysql.DATETIME`, :class:`.mysql.TIMESTAMP` and
:class:`.mysql.TIME` types would be incorrectly placed into the
``timestamp`` attribute, which is unused by MySQL, instead of the
``fsp`` attribute.
fixes #3602

- flake8 test_reflection and rework the type-based tests into

2015-12-07T22:09:11+00:00

individual categories w/ modernized fixtures, assert attributes
within type objects.

- The system by which a :class:`.Column` considers itself to be an

2015-10-07T14:02:45+00:00

"auto increment" column has been changed, such that autoincrement
is no longer implicitly enabled for a :class:`.Table` that has a
composite primary key.  In order to accommodate being able to enable
autoincrement for a composite PK member column while at the same time
maintaining SQLAlchemy's long standing behavior of enabling
implicit autoincrement for a single integer primary key, a third
state has been added to the :paramref:`.Column.autoincrement` parameter
``"auto"``, which is now the default. fixes #3216
- The MySQL dialect no longer generates an extra "KEY" directive when
generating CREATE TABLE DDL for a table using InnoDB with a
composite primary key with AUTO_INCREMENT on a column that isn't the
first column;  to overcome InnoDB's limitation here, the PRIMARY KEY
constraint is now generated with the AUTO_INCREMENT column placed
first in the list of columns.

- make even more tables

2015-02-07T15:22:08+00:00

- break up the tables here to avoid the error we're getting

2015-02-07T04:41:01+00:00

on jenkins

- The MySQL dialect now renders TIMESTAMP with NULL / NOT NULL in

2015-02-05T21:24:45+00:00

all cases, so that MySQL 5.6.6 with the
``explicit_defaults_for_timestamp`` flag enabled will
will allow TIMESTAMP to continue to work as expected when
``nullable=False``.  Existing applications are unaffected as
SQLAlchemy has always emitted NULL for a TIMESTAMP column that
is ``nullable=True``.  fixes #3155

- use provide_metadata for new unique constraint / index tests

2014-10-04T23:06:35+00:00

- add a test for PG reflection of unique index without any unique
constraint
- for PG, don't include 'duplicates_constraint' in the entry
if the index does not actually mirror a constraint
- use a distinct method for unique constraint reflection within table
- catch unique constraint not implemented condition; this may
be within some dialects and also is expected to be supported by
Alembic tests
- migration + changelogs for #3184
- add individual doc notes as well to MySQL, Postgreql
fixes #3184

Reflect unique constraints when reflecting a Table object

2014-09-17T20:19:50+00:00

Calls to reflect a table did not create any UniqueConstraint objects.
The reflection core made no calls to get_unique_constraints and as
a result, the sqlite dialect would never reflect any unique constraints.

MySQL transparently converts unique constraints into unique indexes, but
SQLAlchemy would reflect those as an Index object and as a
UniqueConstraint. The reflection core will now deduplicate the unique
constraints.

PostgreSQL would reflect unique constraints as an Index object and as
a UniqueConstraint object. The reflection core will now deduplicate
the unique indexes.