Hello community,

here is the log from the commit of package python3-alembic for openSUSE:Factory 
checked in at 2015-05-11 19:39:13
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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  
2015-04-30 11:50:32.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python3-alembic.new/python3-alembic.changes     
2015-05-11 19:49:14.000000000 +0200
@@ -1,0 +2,40 @@
+Sat May  9 22:07:22 UTC 2015 - [email protected]
+
+- update to version 0.7.6:
+  * Fixed bug where the case of multiple mergepoints that all have the
+    identical set of ancestor revisions would fail to be upgradable,
+    producing an assertion failure. Merge points were previously
+    assumed to always require at least an UPDATE in alembic_revision
+    from one of the previous revs to the new one, however in this
+    case, if one of the mergepoints has already been reached, the
+    remaining mergepoints have no row to UPDATE therefore they must do
+    an INSERT of their target version.  References: #297
+  * Added support for type comparison functions to be not just per
+    environment, but also present on the custom types themselves, by
+    supplying a method compare_against_backend. Added a new
+    documentation section Comparing Types describing type comparison
+    fully. References: #296
+  * Added a new option EnvironmentContext.configure.literal_binds,
+    which will pass the literal_binds flag into the compilation of SQL
+    constructs when using "offline" mode. This has the effect that SQL
+    objects like inserts, updates, deletes as well as textual
+    statements sent using text() will be compiled such that the
+    dialect will attempt to render literal values “inline”
+    automatically. Only a subset of types is typically supported; the
+    Operations.inline_literal() construct remains as the construct
+    used to force a specific literal representation of a value. The
+    EnvironmentContext.configure.literal_binds flag is added to the
+    "offline" section of the env.py files generated in new
+    environments. References: #255
+  * Fully implemented the copy_from parameter for batch mode, which
+    previously was not functioning. This allows "batch mode" to be
+    usable in conjunction with --sql. References: #289
+  * Repaired support for the BatchOperations.create_index() directive,
+    which was mis-named internally such that the operation within a
+    batch context could not proceed. The create index operation will
+    proceed as part of a larger "batch table recreate" operation only
+    if recreate is set to "always", or if the batch operation includes
+    other instructions that require a table recreate. References:
+    #287
+
+-------------------------------------------------------------------

Old:
----
  alembic-0.7.5.post2.tar.gz

New:
----
  alembic-0.7.6.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python3-alembic.spec ++++++
--- /var/tmp/diff_new_pack.Quvd6p/_old  2015-05-11 19:49:15.000000000 +0200
+++ /var/tmp/diff_new_pack.Quvd6p/_new  2015-05-11 19:49:15.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           python3-alembic
-Version:        0.7.5.post2
+Version:        0.7.6
 Release:        0
 Url:            https://pypi.python.org/pypi/alembic
 Summary:        A database migration tool for SQLAlchemy

++++++ alembic-0.7.5.post2.tar.gz -> alembic-0.7.6.tar.gz ++++++
++++ 3572 lines of diff (skipped)


Reply via email to