]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Don't use cx_Oracle.NATIVE_INT in output type handlers
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 19 Jan 2019 02:30:21 +0000 (21:30 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 19 Jan 2019 15:38:49 +0000 (10:38 -0500)
commitb1ca92625dadce587946df157fac5456b7cf1592
treed51b9d15d59a967e9c92aca26d9b8908fa154aa3
parent7c96b19fad42b820f85e55fc2295c00eb6de5ab0
Don't use cx_Oracle.NATIVE_INT in output type handlers

Fixed regression in integer precision logic due to the refactor of the
cx_Oracle dialect in 1.2.  We now no longer apply the cx_Oracle.NATIVE_INT
type to result columns sending integer values (detected as positive
precision with scale ==0) which encounters integer overflow issues with
values that go beyond the 32 bit boundary.  Instead, the output variable
is left untyped so that cx_Oracle can choose the best option.

Fixes: #4457
Change-Id: I1e3114c2f37bf028fb1f521a3e9789a77e3a7491
(cherry picked from commit 5832f7172907a8151345d95061f93784ce4bb9b1)
doc/build/changelog/unreleased_12/4457.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/oracle/cx_oracle.py
test/dialect/oracle/test_types.py