diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-10-03 14:09:54 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-10-03 15:02:00 -0400 |
commit | e21afbcd8c78e4e3f9400da1a2565472682de825 (patch) | |
tree | b50a003712cff0d1b84e1f6e42b126dbdfaa7ac8 /lib/sqlalchemy/dialects/mysql/pyodbc.py | |
parent | 334bad16792666a096c2cbe2dd8936eaaefa0251 (diff) | |
download | sqlalchemy-e21afbcd8c78e4e3f9400da1a2565472682de825.tar.gz |
call setinputsizes for cx_Oracle.DATETIME
Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a
SQLAlchemy :class:`.Date`, :class:`.DateTime` or :class:`.Time` datatype is
used, so that in the case where a bound parameter is passed as NULL
in some complex queries (in particular this happens with some lazy load
situations), the type is still present. This was removed
in the 1.2 series for arbitrary reasons.
Also adds a suite test for this generic situation.
What's not clear is that do we really need setinputsizes() for all
datatypes if we are supporting NULL in bound parameters.
Fixes: #4886
Change-Id: If99215c31861f9ea6f60a30d47f2f320adc4797f
Diffstat (limited to 'lib/sqlalchemy/dialects/mysql/pyodbc.py')
0 files changed, 0 insertions, 0 deletions