[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2016-06-03 14:58:12
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d318139fdc4c/ Changeset: d318139fdc4c Branch: None User: zzzeek Date: 2016-06-02 17:54:38+00:00 Summary: Skip UniqueConstraint marked by unique=True in tometadata 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 (cherry picked from commit afb466fb8bd9c2f8709e79fd0fce422b83ff1d6b) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a11331857bed/ Changeset: a11331857bed Branch: rel_1_0 User: zzzeek Date: 2016-06-03 14:56:33+00:00 Summary: Merge "Skip UniqueConstraint marked by unique=True in tometadata" into rel_1_0 Affected #: 3 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |