[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2014-01-20 23:14:57
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/49f1807f8f2a/ Changeset: 49f1807f8f2a Branch: None User: zzzeek Date: 2014-01-21 00:06:18 Summary: - simplify the mechanics of PrimaryKeyConstraint with regards to reflection; reflection now updates the PKC in place. - support the use case of the empty PrimaryKeyConstraint in order to specify constraint options; the columns marked as primary_key=True will now be gathered into the columns collection, rather than being ignored. [ticket:2910] - add validation such that column specification should only take place in the PrimaryKeyConstraint directly, or by using primary_key=True flags; if both are present, they have to match exactly, otherwise the condition is assumed to be ambiguous, and a warning is emitted; the old behavior of using the PKC columns only is maintained. Affected #: 7 files https://bitbucket.org/zzzeek/sqlalchemy/commits/417aeaf1453c/ Changeset: 417aeaf1453c Branch: None User: zzzeek Date: 2014-01-21 00:14:02 Summary: - further refine this so that the ordering of columns is maintained as sent to the primary key constraint; existing tests in the PG dialect confirm this. Affected #: 2 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. |