diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-05-18 12:51:40 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-05-18 19:29:16 -0400 |
| commit | c7ae04d1c5c4aa6c6099584ae386d6ab9ef7b290 (patch) | |
| tree | 96f7e6fa64fc7e693018a5f46afe6561d8e401b7 /lib/sqlalchemy/ext/automap.py | |
| parent | d2bacad469c0b07cc707b563e37e835abcf96eb8 (diff) | |
| download | sqlalchemy-c7ae04d1c5c4aa6c6099584ae386d6ab9ef7b290.tar.gz | |
call setinputsizes() for integer types
Altered the Oracle dialect such that when an :class:`.Integer` type is in
use, the cx_Oracle.NUMERIC type is set up for setinputsizes(). In
SQLAlchemy 1.1 and earlier, cx_Oracle.NUMERIC was passed for all numeric
types unconditionally, and in 1.2 this was removed to allow for better
numeric precision. However, for integers, some database/client setups
will fail to coerce boolean values True/False into integers which introduces
regressive behavior when using SQLAlchemy 1.2. Overall, the setinputsizes
logic seems like it will need a lot more flexibility going forward so this
is a start for that.
Change-Id: Ida80cc2c2c37ffc0e05da4b5df2dadfab55a01f2
Fixes: #4259
Diffstat (limited to 'lib/sqlalchemy/ext/automap.py')
0 files changed, 0 insertions, 0 deletions