Sync from SUSE:SLFO:Main python-SQLAlchemy revision 025c248f660927d4566ed28f2a4ef692
This commit is contained in:
@@ -1,3 +1,101 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Apr 22 12:39:48 UTC 2025 - Daniel Garcia <daniel.garcia@suse.com>
|
||||
|
||||
- Update files to support modern and older setuptools, lowercase and
|
||||
uppercase dist-info file, in Factory and Leap.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Apr 1 11:16:59 UTC 2025 - Markéta Machová <mmachova@suse.com>
|
||||
|
||||
- Update to 2.0.40
|
||||
* Support has been re-added for the MySQL-Connector/Python DBAPI
|
||||
using the mysql+mysqlconnector:// URL scheme.
|
||||
* Added support for specifying a list of columns for SET NULL and
|
||||
SET DEFAULT actions of ON DELETE clause of foreign key definition
|
||||
on PostgreSQL.
|
||||
* Implemented support for the GROUPS frame specification in window
|
||||
functions by adding groups option to over() and FunctionElement.over().
|
||||
* Fixed regression in ORM Annotated Declarative class interpretation
|
||||
caused by typing_extension==4.13.0 that introduced a different
|
||||
implementation for TypeAliasType.
|
||||
* More changes, see upstream changelog
|
||||
- Wrap the metadata directory name in a distro-based conditional.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Mar 25 08:18:23 UTC 2025 - Steve Kowalik <steven.kowalik@suse.com>
|
||||
|
||||
- Lowercase metadata directory name.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Thu Mar 13 07:53:14 UTC 2025 - Adrian Schröter <adrian@suse.de>
|
||||
|
||||
- Update to 2.0.39
|
||||
Details can be found here:
|
||||
https://docs.sqlalchemy.org/en/20/changelog/changelog_20.html#change-2.0.39
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Wed Nov 6 14:43:11 UTC 2024 - John Paul Adrian Glaubitz <adrian.glaubitz@suse.com>
|
||||
|
||||
- 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
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 19 07:10:55 UTC 2024 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user