Hello community, here is the log from the commit of package python3-alembic for openSUSE:Factory checked in at 2015-01-20 19:04:06 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python3-alembic (Old) and /work/SRC/openSUSE:Factory/.python3-alembic.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python3-alembic" Changes: -------- --- /work/SRC/openSUSE:Factory/python3-alembic/python3-alembic.changes 2013-11-12 15:21:38.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.python3-alembic.new/python3-alembic.changes 2015-01-20 19:04:07.000000000 +0100 @@ -1,0 +2,542 @@ +Sat Jan 10 18:28:37 UTC 2015 - [email protected] + +- specfile: + * update copyright year + * remove trailing whitespace + +- update to version 0.7.3: + * Fixed regression in new versioning system where upgrade / history + operation would fail on AttributeError if no version files were + present at all. + +- changes from version 0.7.2: + * Adjusted the SQLite backend regarding autogen of unique + constraints to work fully with the current SQLAlchemy 1.0, which + now will report on UNIQUE constraints that have no name. + * Fixed bug in batch where if the target table contained multiple + foreign keys to the same target table, the batch mechanics would + fail with a "table already exists" error. Thanks for the help on + this from Lucas Kahlert. + * Fixed an issue where the MySQL routine to skip + foreign-key-implicit indexes would also catch unnamed unique + indexes, as they would be named after the column and look like the + FK indexes. Pull request courtesy Johannes Erdfelt. + * Repaired a regression in both the MSSQL and Oracle dialects + whereby the overridden "_exec()" method failed to return a + value, as is needed now in the 0.7 series. + +- changes from version 0.7.1: + * The "render_as_batch" flag was inadvertently hardcoded to "True", + so all autogenerates were spitting out batch mode...this has been + fixed so that batch mode again is only when selected in env.py. + * Support for autogenerate of FOREIGN KEY constraints has been + added. These are delivered within the autogenerate process in the + same manner as UNIQUE constraints, including "include_object" + support. Big thanks to Ann Kamyshnikova for doing the heavy + lifting here. + * Added :paramref:`~.Operations.batch_alter_table.naming_convention` + argument to :meth:`.Operations.batch_alter_table`, as this is + necessary in order to drop foreign key constraints; these are + often unnamed on the target database, and in the case that they + are named, SQLAlchemy is as of the 0.9 series not including these + names yet. + * Fixed bug where the "source_schema" argument was not correctly + passed when calling :meth:`.BatchOperations.create_foreign_key`. + Pull request courtesy Malte Marquarding. + * Repaired the inspection, copying and rendering of CHECK + constraints and so-called "schema" types such as Boolean, Enum + within the batch copy system; the CHECK constraint will not be + "doubled" when the table is copied, and additionally the + inspection of the CHECK constraint for its member columns will no + longer fail with an attribute error. + * Added two new arguments + :paramref:`.Operations.batch_alter_table.reflect_args` and + :paramref:`.Operations.batch_alter_table.reflect_kwargs`, so that + arguments may be passed directly to suit the + :class:`~.sqlalchemy.schema.Table` object that will be reflected. + + +- changes from version 0.7.0: + * The "multiple heads / branches" feature has now landed. This is + by far the most significant change Alembic has seen since its + inception; while the workflow of most commands hasn't changed, and + the format of version files and the "alembic_version" table are + unchanged as well, a new suite of features opens up in the case + where multiple version files refer to the same parent, or to the + "base". Merging of branches, operating across distinct named + heads, and multiple independent bases are now all supported. The + feature incurs radical changes to the internals of versioning and + traversal, and should be treated as "beta mode" for the next + several subsequent releases within 0.7. + * In conjunction with support for multiple independent bases, the + specific version directories are now also configurable to include + multiple, user-defined directories. When multiple directories + exist, the creation of a revision file with no down revision + requires that the starting directory is indicated; the creation of + subsequent revisions along that lineage will then automatically + use that directory for new files. + * Added "move and copy" workflow, where a table to be altered is + copied to a new one with the new structure and the old one + dropped, is now implemented for SQLite as well as all database + backends in general using the new + :meth:`.Operations.batch_alter_table` system. This directive + provides a table-specific operations context which gathers column- + and constraint-level mutations specific to that table, and at the + end of the context creates a new table combining the structure of + the old one with the given changes, copies data from old table to + new, and finally drops the old table, renaming the new one to the + existing name. This is required for fully featured SQLite + migrations, as SQLite has very little support for the traditional + ALTER directive. The batch directive is intended to produce code + that is still compatible with other databases, in that the "move + and copy" process only occurs for SQLite by default, while still + providing some level of sanity to SQLite's requirement by allowing + multiple table mutation operations to proceed within one "move and + copy" as well as providing explicit control over when this + operation actually occurs. The "move and copy" feature may be + optionally applied to other backends as well, however dealing with + referential integrity constraints from other tables must still be + handled explicitly. + * Relative revision identifiers as used with "alembic upgrade", + "alembic downgrade" and "alembic history" can be combined with + specific revisions as well, e.g. "alembic upgrade ae10+3", to + produce a migration target relative to the given exact version. + * The "alembic revision" command accepts the "--sql" option to suit + some very obscure use case where the "revision_environment" flag + is set up, so that "env.py" is run when "alembic revision" is run + even though autogenerate isn't specified. As this flag is + otherwise confusing, error messages are now raised if "alembic + revision" is invoked with both "--sql" and "--autogenerate" or + with "--sql" without "revision_environment" being set. + * Added a rule for Postgresql to not render a "drop unique" and + "drop index" given the same name; for now it is assumed that the + "index" is the implicit one Postgreql generates. Future + integration with new SQLAlchemy 1.0 features will improve this to + be more resilient. + * A change in the ordering when columns and constraints are dropped; + autogenerate will now place the "drop constraint" calls *before* + the "drop column" calls, so that columns involved in those + constraints still exist when the constraint is dropped. + * New commands added: "alembic show", "alembic heads" and "alembic + merge". Also, a new option "--verbose" has been added to several + informational commands, such as "alembic history", "alembic + current", "alembic branches", and "alembic heads". "alembic + revision" also contains several new options used within the new + branch management system. The output of commands has been altered + in many cases to support new fields and attributes; the "history" + command in particular now returns it's "verbose" output only if + "--verbose" is sent; without this flag it reverts to it's older + behavior of short line items (which was never changed in the + docs). + * The "--head_only" option to the "alembic current" command is + deprecated; the "current" command now lists just the version + numbers alone by default; use "--verbose" to get at additional + output. + * Added new argument :paramref:`.Config.config_args`, allows a + dictionary of replacement variables to be passed which will serve + as substitution values when an API-produced :class:`.Config` + consumes the ".ini" file. Pull request courtesy Noufal Ibrahim. + * The Oracle dialect sets "transactional DDL" to False by default, + as Oracle does not support transactional DDL. + * Fixed a variety of issues surrounding rendering of Python code + that contains unicode literals. The first is that the + "quoted_name" construct that SQLAlchemy uses to represent table + and column names as well as schema names does not "repr()" + correctly on Py2K when the value contains unicode characters; + therefore an explicit stringification is added to these. + Additionally, SQL expressions such as server defaults were not + being generated in a unicode-safe fashion leading to decode errors + if server defaults contained non-ascii characters. + * The :meth:`.Operations.add_column` directive will now additionally + emit the appropriate "CREATE INDEX" statement if the + :class:`~sqlalchemy.schema.Column` object specifies + "index=True". Pull request courtesy David Szotten. + * The :class:`~sqlalchemy.schema.Table` object is now returned when + the :meth:`.Operations.create_table` method is used. This "Table" + is suitable for use in subsequent SQL operations, in particular + the :meth:`.Operations.bulk_insert` operation. + * Indexes and unique constraints are now included in the + :paramref:`.EnvironmentContext.configure.include_object` + hook. Indexes are sent with type ""index"" and unique constraints + with type ""unique_constraint"". + * Bound parameters are now resolved as "literal" values within the + SQL expression inside of a CheckConstraint(), when rendering the + SQL as a text string; supported for SQLAlchemy 0.8.0 and forward. + * Added a workaround for SQLAlchemy issue #3023 (fixed in 0.9.5) + where a column that's part of an explicit PrimaryKeyConstraint + would not have its "nullable" flag set to False, thus producing a + false autogenerate. Also added a related correction to MySQL + which will correct for MySQL's implicit server default of '0' when + a NULL integer column is turned into a primary key column. + * Repaired issue related to the fix for #208 and others; a composite + foreign key reported by MySQL would cause a KeyError as Alembic + attempted to remove MySQL's implicitly generated indexes from the + autogenerate list. + * If the "alembic_version" table is present in the target metadata, + autogenerate will skip this also. Pull request courtesy Dj + Gilcrease. + * The :paramref:`.EnvironmentContext.configure.version_table` and + :paramref:`.EnvironmentContext.configure.version_table_schema` + arguments are now honored during the autogenerate process, such + that these names will be used as the "skip" names on both the + database reflection and target metadata sides. + * The default value of the + :paramref:`.EnvironmentContext.configure.user_module_prefix` + parameter is **no longer the same as the SQLAlchemy prefix**. When + omitted, user-defined types will now use the "__module__" + attribute of the type class itself when rendering in an + autogenerated module. + * Revision files are now written out using the "'wb'" modifier to + "open()", since Mako reads the templates with "'rb'", thus + preventing CRs from being doubled up as has been observed on + windows. The encoding of the output now defaults to 'utf-8', + which can be configured using a newly added config file parameter + "output_encoding". + * Added support for use of the + :class:`~sqlalchemy.sql.elements.quoted_name` construct when using + the "schema" argument within operations. This allows a name ++++ 345 more lines (skipped) ++++ between /work/SRC/openSUSE:Factory/python3-alembic/python3-alembic.changes ++++ and /work/SRC/openSUSE:Factory/.python3-alembic.new/python3-alembic.changes Old: ---- alembic-0.6.0.tar.gz New: ---- alembic-0.7.3.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-alembic.spec ++++++ --- /var/tmp/diff_new_pack.AkPQJh/_old 2015-01-20 19:04:08.000000000 +0100 +++ /var/tmp/diff_new_pack.AkPQJh/_new 2015-01-20 19:04:08.000000000 +0100 @@ -1,7 +1,7 @@ # # spec file for package python3-alembic # -# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2015 SUSE LINUX Products 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: python3-alembic -Version: 0.6.0 +Version: 0.7.3 Release: 0 Url: https://pypi.python.org/pypi/alembic Summary: A database migration tool for SQLAlchemy ++++++ alembic-0.6.0.tar.gz -> alembic-0.7.3.tar.gz ++++++ ++++ 44545 lines of diff (skipped) -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
