diff options
| author | Leon Anavi <leon.anavi@konsulko.com> | 2021-01-07 00:06:56 +0200 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2021-01-08 08:42:10 -0800 |
| commit | d191a87770b0b35d3a08b4cd634a35810923e3c9 (patch) | |
| tree | 053c24fa0706f2a8d92a88bfa5f039cf2049618a /meta-python/recipes-devtools/python/python-numeric/0001-it-tries-to-define-this-function-differently-than-it.patch | |
| parent | 0c0255a513b1dacba585bac9f4a68fbdbb60e47a (diff) | |
| download | meta-openembedded-d191a87770b0b35d3a08b4cd634a35810923e3c9.tar.gz | |
python3-sqlalchemy: Upgrade 1.3.20 -> 1.3.22
Upgrade to release 1.3.22:
- Fixed regression which occured due to #5755 which implemented
isolation level support for Oracle. It has been reported that
many Oracle accounts don't actually have permission to query
the v$transaction view so this feature has been altered to
gracefully fallback when it fails upon database connect, where
the dialect will assume "READ COMMITTED" is the default
isolation level as was the case prior to SQLAlchemy 1.3.21.
However, explicit use of the Connection.get_isolation_level()
method must now necessarily raise an exception, as Oracle
databases with this restriction explicitly disallow the user
from reading the current isolation level.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python-numeric/0001-it-tries-to-define-this-function-differently-than-it.patch')
0 files changed, 0 insertions, 0 deletions