Hello community, here is the log from the commit of package python-SQLAlchemy for openSUSE:Factory checked in at 2018-04-26 13:37:26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old) and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy" Thu Apr 26 13:37:26 2018 rev:50 rq:599639 version:1.2.7 Changes: -------- --- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes 2018-04-11 13:59:55.755275579 +0200 +++ /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new/python-SQLAlchemy.changes 2018-04-26 13:37:39.592897096 +0200 @@ -1,0 +2,47 @@ +Sat Apr 21 16:35:48 UTC 2018 - [email protected] + +- update to version 1.2.7: + * orm + + [orm] [bug] Fixed regression in 1.2 within sharded query feature + where the new “identity_token” element was not being correctly + considered within the scope of a lazy load operation, when + searching the identity map for a related many-to-one + element. The new behavior will allow for making use of the + “id_chooser” in order to determine the best identity key to + retrieve from the identity map. In order to achieve this, some + refactoring of 1.2’s “identity_token” approach has made some + slight changes to the implementation of ShardedQuery which + should be noted for other derivations of this class. + References: #4228 + + [orm] [bug] Fixed issue in single-inheritance loading where the + use of an aliased entity against a single-inheritance subclass + in conjunction with the Query.select_from() method would cause + the SQL to be rendered with the unaliased table mixed in to the + query, causing a cartesian product. In particular this was + affecting the new “selectin” loader when used against a + single-inheritance subclass. References: #4241 + * sql + + [sql] [bug] Fixed issue where the compilation of an INSERT + statement with the “literal_binds” option that also uses an + explicit sequence and “inline” generation, as on Postgresql and + Oracle, would fail to accommodate the extra keyword argument + within the sequence processing routine. References: #4231 + * postgresql + + [postgresql] [feature] Added new PG type postgresql.REGCLASS + which assists in casting table names to OID values. Pull request + courtesy Sebastian Bank. References: #4160 + + [postgresql] [bug] Fixed bug where the special “not equals” + operator for the Postgresql “range” datatypes such as DATERANGE + would fail to render “IS NOT NULL” when compared to the Python + None value. References: #4229 + * mssql + + [mssql] [bug] Fixed 1.2 regression caused by #4060 where the + query used to reflect SQL Server cross-schema foreign keys was + limiting the criteria incorrectly. References: #4234 + * oracle + + [oracle] [bug] The Oracle NUMBER datatype is reflected as + INTEGER if the precision is NULL and the scale is zero, as this + is how INTEGER values come back when reflected from Oracle’s + tables. Pull request courtesy Kent Bower. + +------------------------------------------------------------------- Old: ---- SQLAlchemy-1.2.6.tar.gz New: ---- SQLAlchemy-1.2.7.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-SQLAlchemy.spec ++++++ --- /var/tmp/diff_new_pack.iqeQzO/_old 2018-04-26 13:37:40.240873346 +0200 +++ /var/tmp/diff_new_pack.iqeQzO/_new 2018-04-26 13:37:40.244873200 +0200 @@ -20,12 +20,12 @@ %define oldpython python %bcond_without tests Name: python-SQLAlchemy -Version: 1.2.6 +Version: 1.2.7 Release: 0 Summary: Database Abstraction Library License: MIT Group: Development/Languages/Python -Url: http://www.sqlalchemy.org +URL: http://www.sqlalchemy.org Source: https://files.pythonhosted.org/packages/source/S/SQLAlchemy/SQLAlchemy-%{version}.tar.gz BuildRequires: %{python_module devel} # Test requirements: ++++++ SQLAlchemy-1.2.6.tar.gz -> SQLAlchemy-1.2.7.tar.gz ++++++ ++++ 6764 lines of diff (skipped)
