Alembic release 0.8.10 is now available.
This release contains a small set of bug fixes. One is prominent, which
is that the alembic_version table now receives a primary key constraint
on the "version_number" column when the table is first created. This is
to provide compatibility with database engines that require that all
tables have primary key constraints.
The "version_number" column has always been considered as a "unique"
column; historically, the table would hold only one row. However when
the "branching" feature was added, alembic_version because a multi-row
table.
The change does not affect any existing alembic_version tables, however
it is safe for an application to add a primary key constraint to this
table. The behavior can also be disabled for new alembic_version
tables using a new flag version_table_pk applied to
EnvironmentContext.configure.
Download Alembic 0.8.10 at:
https://pypi.python.org/pypi/alembic
Changelog:
http://alembic.zzzcomputing.com/en/latest/changelog.html#change-0.8.10
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
Example. See http://stackoverflow.com/help/mcve for a full description.
---
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
