[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2015-10-07 14:05:16
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/61fc1d07160b/ Changeset: 61fc1d07160b Branch: ticket_3216 User: zzzeek Date: 2015-10-07 14:01:35+00:00 Summary: - tweaks Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/414af7b61291/ Changeset: 414af7b61291 Branch: None User: zzzeek Date: 2015-10-07 14:02:45+00:00 Summary: - The system by which a :class:`.Column` considers itself to be an "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. Affected #: 22 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. |