Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-SQLAlchemy for
openSUSE:Factory checked in at 2022-06-17 21:20:10
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1548 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy"
Fri Jun 17 21:20:10 2022 rev:97 rq:982126 version:1.4.37
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
2022-05-06 18:58:15.617285786 +0200
+++
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1548/python-SQLAlchemy.changes
2022-06-17 21:22:24.682770069 +0200
@@ -1,0 +2,24 @@
+Sat Jun 4 08:49:42 UTC 2022 - Dirk M??ller <dmuel...@suse.com>
+
+- update to 1.4.37
+ * details on
https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.37
+ * Fixed issue where using a column_property() construct containing a subquery
+ against an already-mapped column attribute would not correctly apply
+ ORM-compilation behaviors to the subquery, including that the ???IN???
expression
+ added for a single-table inherits expression would fail to be included.
+ * Fixed issue where ORM results would apply incorrect key names to the
+ returned Row objects in the case where the set of columns to be selected
+ were changed, such as when using Select.with_only_columns().
+ * Fixed bug, likely a regression from 1.3, where usage of column names that
+ require bound parameter escaping, more concretely when using Oracle with
+ column names that require quoting such as those that start with an
+ underscore, or in less common cases with some PostgreSQL drivers when using
+ column names that contain percent signs, would cause the ORM versioning
+ feature to not work correctly if the versioning column itself had such a
+ name, as the ORM assumes certain bound parameter naming conventions that
+ were being interfered with via the quotes. This issue is related to #8053
+ and essentially revises the approach towards fixing this, revising the
+ original issue #5653 that created the initial implementation for
+ generalized bound-parameter name quoting.
+
+-------------------------------------------------------------------
Old:
----
SQLAlchemy-1.4.36.tar.gz
New:
----
SQLAlchemy-1.4.37.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.982iuL/_old 2022-06-17 21:22:25.134770314 +0200
+++ /var/tmp/diff_new_pack.982iuL/_new 2022-06-17 21:22:25.138770316 +0200
@@ -20,7 +20,7 @@
%define skip_python2 1
%define oldpython python
Name: python-SQLAlchemy
-Version: 1.4.36
+Version: 1.4.37
Release: 0
Summary: Database Abstraction Library
License: MIT
++++++ SQLAlchemy-1.4.36.tar.gz -> SQLAlchemy-1.4.37.tar.gz ++++++
/work/SRC/openSUSE:Factory/python-SQLAlchemy/SQLAlchemy-1.4.36.tar.gz
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.1548/SQLAlchemy-1.4.37.tar.gz
differ: char 5, line 1
