diff --git a/alembic-0.8.2.tar.gz b/alembic-0.8.2.tar.gz deleted file mode 100644 index f37263e..0000000 --- a/alembic-0.8.2.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a69d65a766801c40e921ca24ae358bf081a990f54b867bbdc3e2a73e975550be -size 931914 diff --git a/alembic-0.8.5.tar.gz b/alembic-0.8.5.tar.gz new file mode 100644 index 0000000..4a21966 --- /dev/null +++ b/alembic-0.8.5.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8ca3b1d806cd39bf8a21d90f5c5822a2173b721ec20f868da38edd45b58cb2 +size 959286 diff --git a/python-alembic.changes b/python-alembic.changes index 711c1d1..775be05 100644 --- a/python-alembic.changes +++ b/python-alembic.changes @@ -1,3 +1,74 @@ +------------------------------------------------------------------- +Thu Apr 7 06:24:53 UTC 2016 - tbechtold@suse.com + +- update to 0.8.5: + - Fixed bug where the columns rendered in a ``PrimaryKeyConstraint`` + in autogenerate would inappropriately render the "key" of the + column, not the name. Pull request courtesy Jesse Dhillon. + - Repaired batch migration support for "schema" types which generate + constraints, in particular the ``Boolean`` datatype which generates + a CHECK constraint. Previously, an alter column operation with this + type would fail to correctly accommodate for the CHECK constraint + on change both from and to this type. In the former case the operation + would fail entirely, in the latter, the CHECK constraint would + not get generated. Both of these issues are repaired. + - Changing a schema type such as ``Boolean`` to a non-schema type would + emit a drop constraint operation which emits ``NotImplementedError`` for + the MySQL dialect. This drop constraint operation is now skipped when + the constraint originates from a schema type. + - A major improvement to the hash id generation function, which for some + reason used an awkward arithmetic formula against uuid4() that produced + values that tended to start with the digits 1-4. Replaced with a + simple substring approach which provides an even distribution. Pull + request courtesy Antti Haapala. + - Added an autogenerate renderer for the :class:`.ExecuteSQLOp` operation + object; only renders if given a plain SQL string, otherwise raises + NotImplementedError. Can be of help with custom autogenerate + sequences that includes straight SQL execution. Pull request courtesy + Jacob Magnusson. + - Batch mode generates a FOREIGN KEY constraint that is self-referential + using the ultimate table name, rather than ``_alembic_batch_temp``. + When the table is renamed from ``_alembic_batch_temp`` back to the + original name, the FK now points to the right name. This + will **not** work if referential integrity is being enforced (eg. SQLite + "PRAGMA FOREIGN_KEYS=ON") since the original table is dropped and + the new table then renamed to that name, however this is now consistent + with how foreign key constraints on **other** tables already operate + with batch mode; these don't support batch mode if referential integrity + is enabled in any case. + - Added a type-level comparator that distinguishes :class:`.Integer`, + :class:`.BigInteger`, and :class:`.SmallInteger` types and + dialect-specific types; these all have "Integer" affinity so previously + all compared as the same. + - Fixed bug where the ``server_default`` parameter of ``alter_column()`` + would not function correctly in batch mode. + - Adjusted the rendering for index expressions such that a :class:`.Column` + object present in the source :class:`.Index` will not be rendered + as table-qualified; e.g. the column name will be rendered alone. + Table-qualified names here were failing on systems such as Postgresql. + - Fixed an 0.8 regression whereby the "imports" dictionary member of + the autogen context was removed; this collection is documented in the + "render custom type" documentation as a place to add new imports. + The member is now known as + :attr:`.AutogenContext.imports` and the documentation is repaired. + - Fixed bug in batch mode where a table that had pre-existing indexes + would create the same index on the new table with the same name, + which on SQLite produces a naming conflict as index names are in a + global namespace on that backend. Batch mode now defers the production + of both existing and new indexes until after the entire table transfer + operation is complete, which also means those indexes no longer take + effect during the INSERT from SELECT section as well; the indexes + are applied in a single step afterwards. + - Added "pytest-xdist" as a tox dependency, so that the -n flag + in the test command works if this is not already installed. + Pull request courtesy Julien Danjou. + - Fixed issue in PG server default comparison where model-side defaults + configured with Python unicode literals would leak the "u" character + from a ``repr()`` into the SQL used for comparison, creating an invalid + SQL expression, as the server-side comparison feature in PG currently + repurposes the autogenerate Python rendering feature to get a quoted + version of a plain string default. + ------------------------------------------------------------------- Wed Aug 26 14:34:12 UTC 2015 - tbechtold@suse.com diff --git a/python-alembic.spec b/python-alembic.spec index cef97b1..92fdb36 100644 --- a/python-alembic.spec +++ b/python-alembic.spec @@ -1,7 +1,7 @@ # # spec file for package python-alembic # -# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,7 +17,7 @@ Name: python-alembic -Version: 0.8.2 +Version: 0.8.5 Release: 0 Url: http://bitbucket.org/zzzeek/alembic Summary: A database migration tool for SQLAlchemy