delta/python-packages/sqlalchemy.git/lib/sqlalchemy/engine/reflection.py, branch pr/183

- copyright 2015

2015-03-10T19:24:28+00:00

- restate sort_tables in terms of a more fine grained

2015-01-02T01:17:06+00:00

sort_tables_and_constraints function.
- The DDL generation system of :meth:`.MetaData.create_all`
and :meth:`.Metadata.drop_all` has been enhanced to in most
cases automatically handle the case of mutually dependent
foreign key constraints; the need for the
:paramref:`.ForeignKeyConstraint.use_alter` flag is greatly
reduced.  The system also works for constraints which aren't given
a name up front; only in the case of DROP is a name required for
at least one of the constraints involved in the cycle.
fixes #3282

- document / work around that dialect_options isn't necessarily there

2014-12-05T17:18:11+00:00

- New Oracle DDL features for tables, indexes: COMPRESS, BITMAP.

2014-12-05T01:08:07+00:00

Patch courtesy Gabor Gombas.
fixes #3127

- 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

Merge branch 'reflect-unique-constraints' of https://bitbucket.org/jerdfelt/sqlalchemy into pr30

2014-10-04T21:47:53+00:00

- cyclomatic complexity; break up reflecttable(), goes from E to B

2014-09-27T22:14:59+00:00

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.

- Added :meth:`.Inspector.get_temp_table_names` and

2014-09-17T19:15:21+00:00

:meth:`.Inspector.get_temp_view_names`; currently, only the
SQLite dialect supports these methods.    The return of temporary
table and view names has been **removed** from SQLite's version
of :meth:`.Inspector.get_table_names` and
:meth:`.Inspector.get_view_names`; other database backends cannot
support this information (such as MySQL), and the scope of operation
is different in that the tables can be local to a session and
typically aren't supported in remote schemas.
fixes #3204

- An adjustment to table/index reflection such that if an index

2014-09-02T18:18:09+00:00

reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180