delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql/schema.py, branch pr/305

Spelling fixes

2016-08-08T13:39:15+00:00

Ensure post-__clause_element__() expression are used in Index

2016-07-31T04:10:04+00:00

The change in Index for 1.1 combined with the fix for
ref #3763 still fails to deliver the correct object
resolved by __clause_element__() to the list of expressions
for compilation.   Make sure we use the expression that's
been unwrapped from __clause_element__().

Change-Id: Ie1df8db5090de665048331786f0024d52851923f
Fixes: #3763

Index should extract __clause_element__() early

2016-07-30T14:11:53+00:00

Fixed bug where :class:`.Index` would fail to extract columns from
compound SQL expressions if those SQL expressions were wrapped inside
of an ORM-style ``__clause_element__()`` construct.  This bug
exists in 1.0.x as well, however in 1.1 is more noticeable as
hybrid_property @expression now returns a wrapped element.

Fixes: #3763

Change-Id: I992536386503a1fb3f2305790abe008d72c44c4a

Allow Table._reset_exported to silently pass

2016-07-25T03:17:11+00:00

Fixed bug in :class:`.Table` where the internal method
``_reset_exported()`` would corrupt the state of the object.  This
method is intended for selectable objects and is called by the ORM
in some cases; an erroneous mapper configuration would could lead the
ORM to call this on on a :class:`.Table` object.

Change-Id: I63fa34ee0cdf16358bb125c556390df79758bcbc
Fixes: #3755

Don't reorder PrimaryKeyConstraint columns if explicit

2016-06-20T16:52:31+00:00

Dialed back the "order the primary key columns per auto-increment"
described in :ref:`change_mysql_3216` a bit, so that if the
:class:`.PrimaryKeyConstraint` is explicitly defined, the order
of columns is maintained exactly, allowing control of this behavior
when necessary.

Change-Id: I9e7902c57a96c15968a6abf53e319acf15680da0
Fixes: #3726

Skip UniqueConstraint marked by unique=True in tometadata

2016-06-02T17:54:07+00:00

Fixes an issue where a Column would be copied with unique=True
and at the same time the UniqueConstraint would also be copied,
leading to duplicate UniqueConstraints in the target table,
when tometadata() is used.   Imitates the same logic used
by index=True/Index to avoid duplicates.  For some reason
a fix was implemented for Index long ago but never for
UniqueConstraint.

Change-Id: Ie622ee912a6fb8bf0ea900a8b09d78c7ebc79fc0
Fixes: #3721

Support "blank" schema when MetaData.schema is set

2016-05-18T15:43:38+00:00

Previously, it was impossible to have a Table that has
None for a schema name when the "schema" parameter on
MetaData was set.  A new symbol sqlalchemy.schema.BLANK_SCHEMA
is added which indicates that the schema name should unconditionally
be set to None.  In particular, this value must be passed within
cross-schema foreign key reflection, so that a Table which
is in the "default" schema can be represented properly.

Fixes: #3716
Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e

- happy new year

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

- convert keys to str for None not sortable against str on py3k

2016-01-12T15:49:14+00:00

- 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