diff --git a/alembic-0.7.7.tar.gz b/alembic-0.7.7.tar.gz deleted file mode 100644 index 96449ac..0000000 --- a/alembic-0.7.7.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:abdeded3f92766d30d2e00015f73573e23f96bcb38037fac199a75445e3e66c6 -size 721855 diff --git a/alembic-0.8.0.tar.gz b/alembic-0.8.0.tar.gz new file mode 100644 index 0000000..cacdca5 --- /dev/null +++ b/alembic-0.8.0.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce73b2935ed20dc41a86025f4200203367083d87520b40526b3fc89f7598f85a +size 918610 diff --git a/python-alembic.changes b/python-alembic.changes index 1cd3d7a..c3ddef8 100644 --- a/python-alembic.changes +++ b/python-alembic.changes @@ -1,3 +1,66 @@ +------------------------------------------------------------------- +Fri Aug 21 12:05:28 UTC 2015 - tbechtold@suse.com + +- update to 0.8.0: + - Added new command alembic edit. This command takes the same arguments + as alembic show, however runs the target script file within $EDITOR. + Makes use of the python-editor library in order to facilitate the + handling of $EDITOR with reasonable default behaviors across platforms. + Pull request courtesy Michel Albert. + - Added new multiple-capable argument --depends-on to the alembic revision + command, allowing depends_on to be established at the command line level + rather than having to edit the file after the fact. depends_on identifiers + may also be specified as branch names at the command line or directly + within the migration file. The values may be specified as partial + revision numbers from the command line which will be resolved to full + revision numbers in the output file. + - The default test runner via “python setup.py test” is now py.test. + nose still works via run_tests.py. + - The internal system for Alembic operations has been reworked to now + build upon an extensible system of operation objects. New operations can + be added to the op. namespace, including that they are available in custom + autogenerate schemes. + - The internal system for autogenerate been reworked to build upon the + extensible system of operation objects present in #302. As part of this + change, autogenerate now produces a full object graph representing a list + of migration scripts to be written as well as operation objects that will + render all the Python code within them; a new hook + EnvironmentContext.configure.process_revision_directives allows end-user + code to fully customize what autogenerate will do, including not just + full manipulation of the Python steps to take but also what file or files + will be written and where. Additionally, autogenerate is now extensible as + far as database objects compared and rendered into scripts; any new + operation directive can also be registered into a series of hooks that + allow custom database/model comparison functions to run as well as to + render new operation directives into autogenerate scripts. + - Fixed bug in batch mode where the batch_op.create_foreign_key() directive + would be incorrectly rendered with the source table and schema names in + the argument list. + - Fixed bug where in the erroneous case that alembic_version contains + duplicate revisions, some commands would fail to process the version history + correctly and end up with a KeyError. The fix allows the versioning logic + to proceed, however a clear error is emitted later when attempting to + update the alembic_version table. + - Implemented support for BatchOperations.create_primary_key() and + BatchOperations.create_check_constraint(). Additionally, table keyword + arguments are copied from the original reflected table, such as the + “mysql_engine” keyword argument. + - Fixed critical issue where a complex series of branches/merges would + bog down the iteration algorithm working over redundant nodes for millions + of cycles. An internal adjustment has been made so that duplicate nodes are + skipped within this iteration. + - The MigrationContext.stamp() method, added as part of the versioning + refactor in 0.7 as a more granular version of command.stamp(), now includes + the “create the alembic_version table if not present” step in the same + way as the command version, which was previously omitted. + - Fixed bug where foreign key options including “onupdate”, “ondelete” would + not render within the op.create_foreign_key() directive, even though they + render within a full ForeignKeyConstraint directive. + - Repaired warnings that occur when running unit tests against SQLAlchemy + 1.0.5 or greater involving the “legacy_schema_aliasing” flag. +- Add python-pytest-cov as BuildRequires +- Add python-python-editor as Requires and BuildRequires + ------------------------------------------------------------------- Fri Jul 24 19:42:39 UTC 2015 - seife+obs@b1-systems.com diff --git a/python-alembic.spec b/python-alembic.spec index aee6592..86fb452 100644 --- a/python-alembic.spec +++ b/python-alembic.spec @@ -17,7 +17,7 @@ Name: python-alembic -Version: 0.7.7 +Version: 0.8.0 Release: 0 Url: http://bitbucket.org/zzzeek/alembic Summary: A database migration tool for SQLAlchemy @@ -33,9 +33,12 @@ BuildRequires: python-SQLAlchemy >= 0.7.6 BuildRequires: python-argparse BuildRequires: python-mock BuildRequires: python-nose >= 0.11 +BuildRequires: python-pytest-cov +BuildRequires: python-python-editor >= 0.3 Requires: python-Mako Requires: python-SQLAlchemy >= 0.7.6 Requires: python-argparse +Requires: python-python-editor >= 0.3 Requires(post): /usr/sbin/update-alternatives Requires(postun): /usr/sbin/update-alternatives %if 0%{?suse_version} && 0%{?suse_version} <= 1110