Hello community,

here is the log from the commit of package python-SQLAlchemy for 
openSUSE:Factory checked in at 2019-06-18 14:48:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
 and      /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.4811 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-SQLAlchemy"

Tue Jun 18 14:48:17 2019 rev:64 rq:708934 version:1.3.4

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes      
2019-04-28 19:59:45.426923946 +0200
+++ 
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.4811/python-SQLAlchemy.changes
    2019-06-18 14:48:20.313700194 +0200
@@ -1,0 +2,91 @@
+Sat Jun  8 23:09:01 UTC 2019 - Arun Persaud <[email protected]>
+
+- update to version 1.3.4:
+  * orm
+    + Fixed issue where the AttributeEvents.active_history flag would
+      not be set for an event listener that propgated to a subclass
+      via the AttributeEvents.propagate flag. This bug has been
+      present for the full span of the AttributeEvents system.
+      References: #4695
+    + Fixed regression where new association proxy system was still
+      not proxying hybrid attributes when they made use of the
+      @hybrid_property.expression decorator to return an alternate SQL
+      expression, or when the hybrid returned an arbitrary
+      PropComparator, at the expression level. This involved futher
+      generalization of the heuristics used to detect the type of
+      object being proxied at the level of QueryableAttribute, to
+      better detect if the descriptor ultimately serves mapped classes
+      or column expressions.  References: #4690
+    + Applied the mapper “configure mutex” against the declarative
+      class mapping process, to guard against the race which can occur
+      if mappers are used while dynamic module import schemes are
+      still in the process of configuring mappers for related
+      classes. This does not guard against all possible race
+      conditions, such as if the concurrent import has not yet
+      encountered the dependent classes as of yet, however it guards
+      against as much as possible within the SQLAlchemy declarative
+      process.  References: #4686
+    + A warning is now emitted for the case where a transient object
+      is being merged into the session with Session.merge() when that
+      object is already transient in the Session. This warns for the
+      case where the object would normally be double-inserted.
+      References: #4647
+    + Fixed regression in new relationship m2o comparison logic first
+      introduced at Improvement to the behavior of many-to-one query
+      expressions when comparing to an attribute that is persisted as
+      NULL and is in an un-fetched state in the mapped instance. Since
+      the attribute has no explicit default, it needs to default to
+      NULL when accessed in a persistent setting.  References: #4676
+  * engine
+    + Moved the “rollback” which occurs during dialect initialization
+      so that it occurs after additional dialect-specific initialize
+      steps, in particular those of the psycopg2 dialect which would
+      inadvertently leave transactional state on the first new
+      connection, which could interfere with some psycopg2-specific
+      APIs which require that no transaction is started. Pull request
+      courtesy Matthew Wilkes.  References: #4663
+  * sql
+    + Fixed that the GenericFunction class was inadvertently
+      registering itself as one of the named functions. Pull request
+      courtesy Adrien Berchet.  References: #4653
+    + Fixed issue where double negation of a boolean column wouldn’t
+      reset the “NOT” operator.  References: #4618
+    + The GenericFunction namespace is being migrated so that function
+      names are looked up in a case-insensitive manner, as SQL
+      functions do not collide on case sensitive differences nor is
+      this something which would occur with user-defined functions or
+      stored procedures. Lookups for functions declared with
+      GenericFunction now use a case insensitive scheme, however a
+      deprecation case is supported which allows two or more
+      GenericFunction objects with the same name of different cases to
+      exist, which will cause case sensitive lookups to occur for that
+      particular name, while emitting a warning at function
+      registration time. Thanks to Adrien Berchet for a lot of work on
+      this complicated feature.  References: #4569
+  * postgresql
+    + Fixed an issue where the “number of rows matched” warning would
+      emit even if the dialect reported
+      “supports_sane_multi_rowcount=False”, as is the case for
+      psycogp2 with use_batch_mode=True and others.  References: #4661
+  * mysql
+    + Added support for DROP CHECK constraint which is required by
+      MySQL 8.0.16 to drop a CHECK constraint; MariaDB supports plain
+      DROP CONSTRAINT. The logic distinguishes between the two
+      syntaxes by checking the server version string for MariaDB
+      presence. Alembic migrations has already worked around this
+      issue by implementing its own DROP for MySQL / MariaDB CHECK
+      constraints, however this change implements it straight in Core
+      so that its available for general use. Pull request courtesy
+      Hannes Hansen.  References: #4650
+  * mssql
+    + Added support for SQL Server filtered indexes, via the
+      mssql_where parameter which works similarly to that of the
+      postgresql_where index function in the PostgreSQL dialect.  See
+      also: Filtered Indexes References: #4657
+    + Added error code 20047 to “is_disconnect” for pymssql. Pull
+      request courtesy Jon Schuff.  References: #4680
+  * misc
+    + Removed errant “sqla_nose.py” symbol from MANIFEST.in which
+      created an undesirable warning message.  References: #4625
+
+-------------------------------------------------------------------

Old:
----
  SQLAlchemy-1.3.3.tar.gz

New:
----
  SQLAlchemy-1.3.4.tar.gz

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

Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.clwxQf/_old  2019-06-18 14:48:22.549699664 +0200
+++ /var/tmp/diff_new_pack.clwxQf/_new  2019-06-18 14:48:22.581699656 +0200
@@ -19,7 +19,7 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define oldpython python
 Name:           python-SQLAlchemy
-Version:        1.3.3
+Version:        1.3.4
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT

++++++ SQLAlchemy-1.3.3.tar.gz -> SQLAlchemy-1.3.4.tar.gz ++++++
++++ 8518 lines of diff (skipped)


Reply via email to