Hello community, here is the log from the commit of package python-SQLAlchemy for openSUSE:Factory checked in at 2018-11-12 09:45:58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old) and /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-SQLAlchemy" Mon Nov 12 09:45:58 2018 rev:57 rq:648375 version:1.2.14 Changes: -------- --- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes 2018-11-06 14:29:02.349483478 +0100 +++ /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new/python-SQLAlchemy.changes 2018-11-12 09:46:51.784696734 +0100 @@ -1,0 +2,30 @@ +Mon Nov 12 06:16:33 UTC 2018 - Arun Persaud <[email protected]> + +- update to version 1.2.14: + * orm + + [orm] [bug] Fixed bug in Session.bulk_update_mappings() where + alternate mapped attribute names would result in the primary key + column of the UPDATE statement being included in the SET clause, + as well as the WHERE clause; while usually harmless, for SQL + Server this can raise an error due to the IDENTITY column. This + is a continuation of the same bug that was fixed in #3849, where + testing was insufficient to catch this additional flaw. + References: #4357 + + [orm] [bug] Fixed a minor performance issue which could in some + cases add unnecessary overhead to result fetching, involving the + use of ORM columns and entities that include those same columns + at the same time within a query. The issue has to do with hash / + eq overhead when referring to the column in different ways. + References: #4347 + * mysql + + [mysql] [bug] Fixed regression caused by #4344 released in + 1.2.13, where the fix for MySQL 8.0’s case sensitivity problem + with referenced column names when reflecting foreign key + referents is worked around using the information_schema.columns + view. The workaround was failing on OSX / + lower_case_table_names=2 which produces non-matching casing for + the information_schema.columns vs. that of SHOW CREATE TABLE, so + in case-insensitive SQL modes case-insensitive matching is now + used. References: #4361 + +------------------------------------------------------------------- Old: ---- SQLAlchemy-1.2.13.tar.gz New: ---- SQLAlchemy-1.2.14.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-SQLAlchemy.spec ++++++ --- /var/tmp/diff_new_pack.vIhWoF/_old 2018-11-12 09:46:52.260696012 +0100 +++ /var/tmp/diff_new_pack.vIhWoF/_new 2018-11-12 09:46:52.260696012 +0100 @@ -20,7 +20,7 @@ %define oldpython python %bcond_without tests Name: python-SQLAlchemy -Version: 1.2.13 +Version: 1.2.14 Release: 0 Summary: Database Abstraction Library License: MIT ++++++ SQLAlchemy-1.2.13.tar.gz -> SQLAlchemy-1.2.14.tar.gz ++++++ ++++ 6156 lines of diff (skipped)
