From 2e79e0fcf7087002661f38a014af03088fcd121ad227f09f777b111f1d919fad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Chv=C3=A1tal?= Date: Sun, 25 Aug 2019 23:03:25 +0000 Subject: [PATCH] Accepting request 725972 from home:apersaud:branches:devel:languages:python update to latest version OBS-URL: https://build.opensuse.org/request/show/725972 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-SQLAlchemy?expand=0&rev=149 --- SQLAlchemy-1.3.6.tar.gz | 3 -- SQLAlchemy-1.3.7.tar.gz | 3 ++ python-SQLAlchemy.changes | 98 +++++++++++++++++++++++++++++++++++++++ python-SQLAlchemy.spec | 4 +- 4 files changed, 103 insertions(+), 5 deletions(-) delete mode 100644 SQLAlchemy-1.3.6.tar.gz create mode 100644 SQLAlchemy-1.3.7.tar.gz diff --git a/SQLAlchemy-1.3.6.tar.gz b/SQLAlchemy-1.3.6.tar.gz deleted file mode 100644 index 7a2c14a..0000000 --- a/SQLAlchemy-1.3.6.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:217e7fc52199a05851eee9b6a0883190743c4fb9c8ac4313ccfceaffd852b0ff -size 5907328 diff --git a/SQLAlchemy-1.3.7.tar.gz b/SQLAlchemy-1.3.7.tar.gz new file mode 100644 index 0000000..7991c77 --- /dev/null +++ b/SQLAlchemy-1.3.7.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0459bf0ea6478f3e904de074d65769a11d74cdc34438ab3159250c96d089aef0 +size 5914400 diff --git a/python-SQLAlchemy.changes b/python-SQLAlchemy.changes index ec37d96..36aacb1 100644 --- a/python-SQLAlchemy.changes +++ b/python-SQLAlchemy.changes @@ -1,3 +1,101 @@ +------------------------------------------------------------------- +Sun Aug 25 17:59:04 UTC 2019 - Arun Persaud + +- update to version 1.3.7: + * orm + + Fixed regression caused by new selectinload for many-to-one + logic where a primaryjoin condition not based on real foreign + keys would cause KeyError if a related object did not exist for + a given key value on the parent object. References: #4777 + + Fixed bug where using Query.first() or a slice expression in + conjunction with a query that has an expression based “offset” + applied would raise TypeError, due to an “or” conditional + against “offset” that did not expect it to be a SQL expression + as opposed to an integer or None. References: #4803 + * sql + + Fixed issue where Index object which contained a mixture of + functional expressions which were not resolvable to a particular + column, in combination with string-based column names, would + fail to initialize its internal state correctly leading to + failures during DDL compilation. References: #4778 + + Fixed bug where TypeEngine.column_expression() method would not + be applied to subsequent SELECT statements inside of a UNION or + other CompoundSelect, even though the SELECT statements are + rendered at the topmost level of the statement. New logic now + differentiates between rendering the column expression, which is + needed for all SELECTs in the list, vs. gathering the returned + data type for the result row, which is needed only for the first + SELECT. References: #4787 + + Fixed issue where internal cloning of SELECT constructs could + lead to a key error if the copy of the SELECT changed its state + such that its list of columns changed. This was observed to be + occurring in some ORM scenarios which may be unique to 1.3 and + above, so is partially a regression fix. References: #4780 + * postgresql + + Added new dialect flag for the psycopg2 dialect, + executemany_mode which supersedes the previous experimental + use_batch_mode flag. executemany_mode supports both the “execute + batch” and “execute values” functions provided by psycopg2, the + latter which is used for compiled insert() constructs. Pull + request courtesy Yuval Dinari. See also: Psycopg2 Fast + Execution Helpers; References: #4623 + * mysql + + The MySQL dialects will emit “SET NAMES” at the start of a + connection when charset is given to the MySQL driver, to appease + an apparent behavior observed in MySQL 8.0 that raises a + collation error when a UNION includes string columns unioned + against columns of the form CAST(NULL AS CHAR(..)), which is + what SQLAlchemy’s polymorphic_union function does. The issue + seems to have affected PyMySQL for at least a year, however has + recently appeared as of mysqlclient 1.4.4 based on changes in + how this DBAPI creates a connection. As the presence of this + directive impacts three separate MySQL charset settings which + each have intricate effects based on their presense, SQLAlchemy + will now emit the directive on new connections to ensure correct + behavior. References: #4804 + + Added another fix for an upstream MySQL 8 issue where a case + sensitive table name is reported incorrectly in foreign key + constraint reflection, this is an extension of the fix first + added for #4344 which affects a case sensitive column name. The + new issue occurs through MySQL 8.0.17, so the general logic of + the 88718 fix remains in place. See also: + https://bugs.mysql.com/bug.php?id=96365 - upstream bug; + References: #4751 + + Added reserved words ARRAY and MEMBER to the MySQL reserved + words list, as MySQL 8.0 has now made these reserved. + References: #4783 + * sqlite + + The dialects that support json are supposed to take arguments + json_serializer and json_deserializer at the create_engine() + level, however the SQLite dialect calls them _json_serilizer and + _json_deserilalizer. The names have been corrected, the old + names are accepted with a change warning, and these parameters + are now documented as create_engine.json_serializer and + create_engine.json_deserializer. References: #4798 + + Fixed bug where usage of “PRAGMA table_info” in SQLite dialect + meant that reflection features to detect for table existence, + list of table columns, and list of foreign keys, would default + to any table in any attached database, when no schema name was + given and the table did not exist in the base schema. The fix + explicitly runs PRAGMA for the ‘main’ schema and then the ‘temp’ + schema if the ‘main’ returned no rows, to maintain the behavior + of tables + temp tables in the “no schema” namespace, attached + tables only in the “schema” namespace. References: #4793 + * mssql + + Added new mssql.try_cast() construct for SQL Server which emits + “TRY_CAST” syntax. Pull request courtesy Leonel Atencio. + References: #4782 + * misc + + Fixed issue in event system where using the once=True flag with + dynamically generated listener functions would cause event + registration of future events to fail if those listener + functions were garbage collected after they were used, due to an + assumption that a listened function is strongly referenced. The + “once” wrapped is now modified to strongly reference the inner + function persistently, and documentation is updated that using + “once” does not imply automatic de-registration of listener + functions. References: #4794 + ------------------------------------------------------------------- Mon Jul 22 16:08:19 UTC 2019 - Todd R diff --git a/python-SQLAlchemy.spec b/python-SQLAlchemy.spec index 3da99e3..e570566 100644 --- a/python-SQLAlchemy.spec +++ b/python-SQLAlchemy.spec @@ -19,12 +19,12 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} %define oldpython python Name: python-SQLAlchemy -Version: 1.3.6 +Version: 1.3.7 Release: 0 Summary: Database Abstraction Library License: MIT Group: Development/Languages/Python -URL: http://www.sqlalchemy.org +URL: https://www.sqlalchemy.org Source: https://files.pythonhosted.org/packages/source/S/SQLAlchemy/SQLAlchemy-%{version}.tar.gz # devel is needed for optional C extensions cprocessors.so, cresultproxy.so and cutils.so BuildRequires: %{python_module devel}