Hello community,

here is the log from the commit of package python-SQLAlchemy for 
openSUSE:Factory checked in at 2018-08-27 12:59:43
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
 and      /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-SQLAlchemy"

Mon Aug 27 12:59:43 2018 rev:54 rq:631547 version:1.2.11

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes      
2018-07-14 20:27:44.264573947 +0200
+++ /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new/python-SQLAlchemy.changes 
2018-08-27 12:59:45.540843017 +0200
@@ -1,0 +2,60 @@
+Sat Aug 25 18:12:02 UTC 2018 - [email protected]
+
+- update to version 1.2.11:
+  * orm declarative
+    + [bug] [declarative] [orm] Fixed issue in previously untested use
+      case, allowing a declarative mapped class to inherit from a
+      classically-mapped class outside of the declarative base,
+      including that it accommodates for unmapped intermediate
+      classes. An unmapped intermediate class may specify
+      __abstract__, which is now interpreted correctly, or the
+      intermediate class can remain unmarked, and the classically
+      mapped base class will be detected within the hierarchy
+      regardless. In order to anticipate existing scenarios which may
+      be mixing in classical mappings into existing declarative
+      hierarchies, an error is now raised if multiple mapped bases are
+      detected for a given class.   References: #4321
+  * sql
+    + [sql] [bug] Fixed issue that is closely related to #3639 where
+      an expression rendered in a boolean context on a non-native
+      boolean backend would be compared to 1/0 even though it is
+      already an implcitly boolean expression, when
+      ColumnElement.self_group() were used. While this does not affect
+      the user-friendly backends (MySQL, SQLite) it was not handled by
+      Oracle (and possibly SQL Server). Whether or not the expression
+      is implicitly boolean on any database is now determined up front
+      as an additional check to not generate the integer comparison
+      within the compliation of the statement.  References: #4320
+    + [sql] [bug] Added missing window function parameters
+      WithinGroup.over.range_ and WithinGroup.over.rows parameters to
+      the WithinGroup.over() and FunctionFilter.over() methods, to
+      correspond to the range/rows feature added to the “over” method
+      of SQL functions as part of #3049 in version 1.1.  References:
+      #4322
+    + [sql] [bug] Fixed bug where the multi-table support for UPDATE
+      and DELETE statements did not consider the additional FROM
+      elements as targets for correlation, when a correlated SELECT
+      were also combined with the statement. This change now includes
+      that a SELECT statement in the WHERE clause for such a statement
+      will try to auto-correlate back to these additional tables in
+      the parent UPDATE/DELETE or unconditionally correlate if
+      Select.correlate() is used. Note that auto-correlation raises an
+      error if the SELECT statement would have no FROM clauses as a
+      result, which can now occur if the parent UPDATE/DELETE
+      specifies the same tables in its additional set of tables;
+      specify Select.correlate() explicitly to resolve.  References:
+      #4313
+  * oracle
+    + [oracle] [bug] For cx_Oracle, Integer datatypes will now be
+      bound to “int”, per advice from the cx_Oracle
+      developers. Previously, using cx_Oracle.NUMBER caused a loss in
+      precision within the cx_Oracle 6.x series.  References: #4309
+  * misc
+    + [bug] [py3k] Started importing “collections” from
+      “collections.abc” under Python 3.3 and greater for Python 3.8
+      compatibility. Pull request courtesy Nathaniel Knight.
+    + Fixed issue where the “schema” name used for a SQLite database
+      within table reflection would not quote the schema name
+      correctly. Pull request courtesy Phillip Cloud.
+
+-------------------------------------------------------------------

Old:
----
  SQLAlchemy-1.2.10.tar.gz

New:
----
  SQLAlchemy-1.2.11.tar.gz

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

Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.7XSFyx/_old  2018-08-27 12:59:45.964843480 +0200
+++ /var/tmp/diff_new_pack.7XSFyx/_new  2018-08-27 12:59:45.968843484 +0200
@@ -20,7 +20,7 @@
 %define oldpython python
 %bcond_without tests
 Name:           python-SQLAlchemy
-Version:        1.2.10
+Version:        1.2.11
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT

++++++ SQLAlchemy-1.2.10.tar.gz -> SQLAlchemy-1.2.11.tar.gz ++++++
++++ 9389 lines of diff (skipped)


Reply via email to