Accepting request 584191 from home:apersaud:branches:devel:languages:python

update to latest version

OBS-URL: https://build.opensuse.org/request/show/584191
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-SQLAlchemy?expand=0&rev=106

python-SQLAlchemy.changes

@@ -1,3 +1,49 @@
+-------------------------------------------------------------------
+Thu Mar  8 04:50:46 UTC 2018 - arun@gmx.de
+
+- update to version 1.2.5:
+  * orm
+    + [orm] [feature] Added new feature
+      Query.only_return_tuples(). Causes the Query object to return
+      keyed tuple objects unconditionally even if the query is against
+      a single entity. Pull request courtesy Eric Atkin.
+    + [orm] [bug] Fixed bug in new “polymorphic selectin” loading when
+      a selection of polymorphic objects were to be partially loaded
+      from a relationship lazy loader, leading to an “empty IN”
+      condition within the load that raises an error for the “inline”
+      form of “IN”. References: #4199
+    + [orm] [bug] Fixed 1.2 regression where a mapper option that
+      contains an AliasedClass object, as is typical when using the
+      QueryableAttribute.of_type() method, could not be pickled. 1.1’s
+      behavior was to omit the aliased class objects from the path, so
+      this behavior is restored.  References: #4209
+  * sql
+    + [sql] [bug] Fixed bug in :class:.`CTE` construct along the same
+      lines as that of #4204 where a CTE that was aliased would not
+      copy itself correctly during a “clone” operation as is frequent
+      within the ORM as well as when using the ClauseElement.params()
+      method.  References: #4210
+    + [sql] [bug] Fixed bug in CTE rendering where a CTE that was also
+      turned into an Alias would not render its “ctename AS aliasname”
+      clause appropriately if there were more than one reference to
+      the CTE in a FROM clause.  References: #4204
+    + [sql] [bug] Fixed bug in new “expanding IN parameter” feature
+      where the bind parameter processors for values wasn’t working at
+      all, tests failed to cover this pretty basic case which includes
+      that ENUM values weren’t working.  References: #4198
+  * postgresql
+    + [postgresql] [bug] [py3k] Fixed bug in Postgresql COLLATE /
+      ARRAY adjustment first introduced in #4006 where new behaviors
+      in Python 3.7 regular expressions caused the fix to fail.  This
+      change is also backported to: 1.1.18 References: #4208
+  * mysql
+    + [mysql] [bug] MySQL dialects now query the server version using
+      SELECT @@version explicitly to the server to ensure we are
+      getting the correct version information back. Proxy servers like
+      MaxScale interfere with the value that is passed to the DBAPI’s
+      connection.server_version value so this is no longer reliable.
+      This change is also backported to: 1.1.18 References: #4205
+
 -------------------------------------------------------------------
 Fri Feb 23 23:48:41 UTC 2018 - arun@gmx.de