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 2024-11-07 16:23:43
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2020 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy"
Thu Nov 7 16:23:43 2024 rev:119 rq:1221792 version:2.0.36
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
2024-08-20 16:12:52.660876255 +0200
+++
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new.2020/python-SQLAlchemy.changes
2024-11-07 16:23:43.988528717 +0100
@@ -1,0 +2,63 @@
+Wed Nov 6 14:43:11 UTC 2024 - John Paul Adrian Glaubitz
<[email protected]>
+
+- Update to 2.0.36
+ * Fixed bug where SQL functions passed to
+ :paramref:`_schema.Column.server_default` would not be rendered with the
+ particular form of parenthesization now required by newer versions of MySQL
+ and MariaDB. Pull request courtesy of huuya.
+ * Fixed bug in ORM bulk update/delete where using RETURNING with bulk
+ update/delete in combination with ``populate_existing`` would fail to
+ accommodate the ``populate_existing`` option.
+ * Continuing from :ticket:`11912`, columns marked with
+ :paramref:`.mapped_column.onupdate`,
+ :paramref:`.mapped_column.server_onupdate`, or :class:`.Computed` are now
+ refreshed in ORM instances when running an ORM enabled UPDATE with WHERE
+ criteria, even if the statement does not use RETURNING or
+ ``populate_existing``.
+ * Added new parameter :paramref:`_orm.mapped_column.hash` to ORM constructs
+ such as :meth:`_orm.mapped_column`, :meth:`_orm.relationship`, etc.,
+ which is interpreted for ORM Native Dataclasses in the same way as other
+ dataclass-specific field parameters.
+ * Fixed bug in reflection of table comments where unrelated text would be
+ returned if an entry in the ``pg_description`` table happened to share the
+ same oid (objoid) as the table being reflected.
+ * Fixed regression caused by fixes to joined eager loading in :ticket:`11449`
+ released in 2.0.31, where a particular joinedload case could not be
+ asserted correctly. We now have an example of that case so the assertion
+ has been repaired to allow for it.
+ * Improved the error message emitted when trying to map as dataclass a class
+ while also manually providing the ``__table__`` attribute.
+ This usage is currently not supported.
+ * Improved a query used for the MySQL 8 backend when reflecting foreign keys
+ to be better optimized. Previously, for a database that had millions of
+ columns across all tables, the query could be prohibitively slow; the query
+ has been reworked to take better advantage of existing indexes.
+ * Datatypes that are binary based such as :class:`.VARBINARY` will resolve to
+ :class:`.LargeBinary` when the :meth:`.TypeEngine.as_generic()` method is
+ called.
+ * The :class:`.postgresql.JSON` and :class:`.postgresql.JSONB` datatypes will
+ now render a "bind cast" in all cases for all PostgreSQL backends,
+ including psycopg2, whereas previously it was only enabled for some
+ backends. This allows greater accuracy in allowing the database server to
+ recognize when a string value is to be interpreted as JSON.
+ * Refined the check which the ORM lazy loader uses to detect "this would be
+ loading by primary key and the primary key is NULL, skip loading" to take
+ into account the current setting for the
+ :paramref:`.orm.Mapper.allow_partial_pks` parameter. If this parameter is
+ ``False``, then a composite PK value that has partial NULL elements should
+ also be skipped. This can apply to some composite overlapping foreign key
+ configurations.
+ * Fixed bug in ORM "update with WHERE clause" feature where an explicit
+ ``.returning()`` would interfere with the "fetch" synchronize strategy due
+ to an assumption that the ORM mapped class featured the primary key columns
+ in a specific position within the RETURNING. This has been fixed to use
+ appropriate ORM column targeting.
+ * Fixed regression from 1.4 where some datatypes such as those derived from
+ :class:`.TypeDecorator` could not be pickled when they were part of a
+ larger SQL expression composition due to internal supporting structures
+ themselves not being pickleable.
+- Adjust upstream source name in spec file
+- For changes between 2.0.33 through 2.0.34 see the upstream changelog
+ * https://docs.sqlalchemy.org/en/20/changelog
+
+-------------------------------------------------------------------
Old:
----
SQLAlchemy-2.0.32.tar.gz
New:
----
sqlalchemy-2.0.36.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.2ljbRS/_old 2024-11-07 16:23:44.764560922 +0100
+++ /var/tmp/diff_new_pack.2ljbRS/_new 2024-11-07 16:23:44.768561088 +0100
@@ -18,12 +18,12 @@
%{?sle15_python_module_pythons}
Name: python-SQLAlchemy
-Version: 2.0.32
+Version: 2.0.36
Release: 0
Summary: Database Abstraction Library
License: MIT
URL: https://www.sqlalchemy.org
-Source:
https://files.pythonhosted.org/packages/source/S/SQLAlchemy/SQLAlchemy-%{version}.tar.gz
+Source:
https://files.pythonhosted.org/packages/source/s/sqlalchemy/sqlalchemy-%{version}.tar.gz
Source1: SQLAlchemy.keyring
# devel is needed for optional C extensions cprocessors.so, cresultproxy.so
and cutils.so
BuildRequires: %{python_module Cython >= 3}
@@ -71,7 +71,7 @@
reference for python-SQLAlchemy.
%prep
-%autosetup -p1 -n SQLAlchemy-%{version}
+%autosetup -p1 -n sqlalchemy-%{version}
rm -rf doc/build # Remove unnecessary scripts for building documentation
sed -i 's/\r$//' examples/dynamic_dict/dynamic_dict.py
