python/python-alembic
SHA256
15
0
Fork 0
forked from pool/python-alembic
Code Pull Requests Activity

Accepting request 327218 from devel:languages:python

Browse Source 
1

OBS-URL: https://build.opensuse.org/request/show/327218
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-alembic?expand=0&rev=22
This commit is contained in:
Stephan Kulow
2015-08-27 06:58:01 +00:00
committed by Git OBS Bridge
parent fed0b6d428 018bc9367a
commit fccca7537a
4 changed files with 106 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
alembic-0.7.7.tar.gz
View File

@@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:abdeded3f92766d30d2e00015f73573e23f96bcb38037fac199a75445e3e66c6
size 721855

3
alembic-0.8.2.tar.gz Normal file
View File

@@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a69d65a766801c40e921ca24ae358bf081a990f54b867bbdc3e2a73e975550be
size 931914

99
python-alembic.changes
View File

@@ -1,3 +1,102 @@
-------------------------------------------------------------------
Wed Aug 26 14:34:12 UTC 2015 - tbechtold@suse.com
- update to 0.8.2:
- Added workaround in new foreign key option detection feature for MySQL’s
consideration of the “RESTRICT” option being the default, for which no
value is reported from the database; the MySQL impl now corrects for when
the model reports RESTRICT but the database reports nothing. A similar
rule is in the default FK comparison to accommodate for the default
“NO ACTION” setting being present in the model but not necessarily
reported by the database, or vice versa.
- A custom EnvironmentContext.configure.process_revision_directives hook
can now generate op directives within the UpgradeOps and DowngradeOps
containers that will be generated as Python code even when the
--autogenerate flag is False; provided that revision_environment=True,
the full render operation will be run even in “offline” mode.
- Implemented support for autogenerate detection of changes in the ondelete,
onupdate, initially and deferrable attributes of ForeignKeyConstraint
objects on SQLAlchemy backends that support these on reflection (as of
SQLAlchemy 1.0.8 currently Postgresql for all four, MySQL for ondelete
and onupdate only). A constraint object that modifies these values will
be reported as a “diff” and come out as a drop/create of the constraint
with the modified values. The fields are ignored for backends which
don’t reflect these attributes (as of SQLA 1.0.8 this includes SQLite,
Oracle, SQL Server, others).
- Repaired the render operation for the ops.AlterColumnOp object to succeed
when the “existing_type” field was not present.
- Fixed a regression 0.8 whereby the “multidb” environment template failed
to produce independent migration script segments for the output template.
This was due to the reorganization of the script rendering system for 0.8.
To accommodate this change, the MigrationScript structure will in the case
of multiple calls to MigrationContext.run_migrations() produce lists for
the MigrationScript.upgrade_ops and MigrationScript.downgrade_ops attributes;
each UpgradeOps and DowngradeOps instance keeps track of its own upgrade_token
and downgrade_token, and each are rendered individually.
-------------------------------------------------------------------
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

5
python-alembic.spec
View File

@@ -17,7 +17,7 @@
Name: python-alembic
Version: 0.7.7
Version: 0.8.2
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