Accepting request 528859 from home:apersaud:branches:devel:languages:python
update to latest version OBS-URL: https://build.opensuse.org/request/show/528859 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-SQLAlchemy?expand=0&rev=94
This commit is contained in:
@@ -1,3 +1,61 @@
|
||||
-------------------------------------------------------------------
|
||||
Mon Sep 25 16:11:55 UTC 2017 - arun@gmx.de
|
||||
|
||||
- update to version 1.1.14:
|
||||
* orm
|
||||
+ [orm] [bug] Fixed bug in Session.merge() following along similar
|
||||
lines as that of #4030, where an internal check for a target
|
||||
object in the identity map could lead to an error if it were to
|
||||
be garbage collected immediately before the merge routine
|
||||
actually retrieves the object. References: #4069
|
||||
+ [orm] [bug] Fixed bug where an undefer_group() option would not
|
||||
be recognized if it extended from a relationship that was
|
||||
loading using joined eager loading. Additionally, as the bug led
|
||||
to excess work being performed, Python function call counts are
|
||||
also improved by 20% within the initial calculation of result
|
||||
set columns, complementing the joined eager load improvements of
|
||||
#3915. References: #4048
|
||||
+ [orm] [bug] Fixed race condition in ORM identity map which would
|
||||
cause objects to be inappropriately removed during a load
|
||||
operation, causing duplicate object identities to occur,
|
||||
particularly under joined eager loading which involves
|
||||
deduplication of objects. The issue is specific to garbage
|
||||
collection of weak references and is observed only under the
|
||||
Pypy interpreter. References: #4068
|
||||
+ [orm] [bug] Fixed bug in Session.merge() where objects in a
|
||||
collection that had the primary key attribute set to None for a
|
||||
key that is typically autoincrementing would be considered to be
|
||||
a database-persisted key for part of the internal deduplication
|
||||
process, causing only one object to actually be inserted in the
|
||||
database. References: #4056
|
||||
+ [orm] [bug] An InvalidRequestError is raised when a synonym() is
|
||||
used against an attribute that is not against a MapperProperty,
|
||||
such as an association proxy. Previously, a recursion overflow
|
||||
would occur trying to locate non-existent attributes. References: #4067
|
||||
* sql
|
||||
+ [sql] [bug] Altered the range specification for window functions
|
||||
to allow for two of the same PRECEDING or FOLLOWING keywords in
|
||||
a range by allowing for the left side of the range to be
|
||||
positive and for the right to be negative, e.g. (1, 3) is “1
|
||||
FOLLOWING AND 3 FOLLOWING”. References: #4053
|
||||
|
||||
- changes from version 1.1.13:
|
||||
* oracle
|
||||
+ [oracle] [bug] [py2k] [performance] Fixed performance regression
|
||||
caused by the fix for #3937 where cx_Oracle as of version 5.3
|
||||
dropped the .UNICODE symbol from its namespace, which was
|
||||
interpreted as cx_Oracle’s “WITH_UNICODE” mode being turned on
|
||||
unconditionally, which invokes functions on the SQLAlchemy side
|
||||
which convert all strings to unicode unconditionally and causing
|
||||
a performance impact. In fact, per cx_Oracle’s author the
|
||||
“WITH_UNICODE” mode has been removed entirely as of 5.1, so the
|
||||
expensive unicode conversion functions are no longer necessary
|
||||
and are disabled if cx_Oracle 5.1 or greater is detected under
|
||||
Python 2. The warning against “WITH_UNICODE” mode that was
|
||||
removed under #3937 is also restored.
|
||||
This change is also backported to: 1.0.19
|
||||
References: #4035
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Aug 8 19:39:50 UTC 2017 - tbechtold@suse.com
|
||||
|
||||
|
||||
Reference in New Issue
Block a user