Hello community,
here is the log from the commit of package python3-SQLAlchemy for
openSUSE:Factory checked in at 2016-10-22 13:23:14
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python3-SQLAlchemy (Old)
and /work/SRC/openSUSE:Factory/.python3-SQLAlchemy.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python3-SQLAlchemy"
Changes:
--------
--- /work/SRC/openSUSE:Factory/python3-SQLAlchemy/python3-SQLAlchemy.changes
2016-10-20 23:09:42.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.python3-SQLAlchemy.new/python3-SQLAlchemy.changes
2016-10-22 13:23:23.000000000 +0200
@@ -1,0 +2,39 @@
+Fri Oct 21 04:33:20 UTC 2016 - [email protected]
+
+- update to version 1.1.2:
+ * orm
+ + [orm] [bug] Fixed bug involving the rule to disable a joined
+ collection eager loader on the other side of a many-to-one lazy
+ loader, first added in #1495, where the rule would fail if the
+ parent object had some other lazyloader-bound query options
+ associated with it.
+ + [orm] [bug] Fixed self-referential entity, deferred column
+ loading issue in a similar style as that of #3431, #3811 where
+ an entity is present in multiple positions within the row due to
+ self-referential eager loading; when the deferred loader only
+ applies to one of the paths, the “present” column loader will
+ now override the deferred non- load for that entity regardless
+ of row ordering.
+ * sql
+ + [sql] [bug] Fixed a regression caused by a newly added function
+ that performs the “wrap callable” function of sql
+ DefaultGenerator objects, an attribute error raised for
+ __module__ when the default callable was a functools.partial or
+ other object that doesn’t have a __module__ attribute.
+ + [sql] [bug] [postgresql] Fixed regression in Enum type where
+ event handlers were not transferred in the case of the type
+ object being copied, due to a conflicting copy() method added as
+ part of #3250. This copy occurs normally in situations when the
+ column is copied, such as in tometadata() or when using
+ declarative mixins with columns. The event handler not being
+ present would impact the constraint being created for a
+ non-native enumerated type, but more critically the ENUM object
+ on the PostgreSQL backend.
+ * postgresql
+ + [postgresql] [bug] [sql] Changed the naming convention used when
+ generating bound parameters for a multi-VALUES insert statement,
+ so that the numbered parameter names don’t conflict with the
+ anonymized parameters of a WHERE clause, as is now common in a
+ PostgreSQL ON CONFLICT construct.
+
+-------------------------------------------------------------------
Old:
----
SQLAlchemy-1.1.1.tar.gz
New:
----
SQLAlchemy-1.1.2.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python3-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.UQP3cp/_old 2016-10-22 13:23:24.000000000 +0200
+++ /var/tmp/diff_new_pack.UQP3cp/_new 2016-10-22 13:23:24.000000000 +0200
@@ -17,7 +17,7 @@
Name: python3-SQLAlchemy
-Version: 1.1.1
+Version: 1.1.2
Release: 0
Url: http://www.sqlalchemy.org
Summary: Database Abstraction Library
++++++ SQLAlchemy-1.1.1.tar.gz -> SQLAlchemy-1.1.2.tar.gz ++++++
++++ 11884 lines of diff (skipped)
