as the DATE type in Oracle stores full date+time objects,
that's what you'll get. Note that the generic types.Date
type *will* still call value.date() on incoming values,
however. When reflecting a table, the reflected type
will be 'DATE'.
- "out" parameters require a type that is supported by
cx_oracle. An error will be raised if no cx_oracle
type can be found.
+ - Oracle 'DATE' now does not perform any result processing,
+ as the DATE type in Oracle stores full date+time objects,
+ that's what you'll get. Note that the generic types.Date
+ type *will* still call value.date() on incoming values,
+ however. When reflecting a table, the reflected type
+ will be 'DATE'.
- sqlite
- Added "native_datetime=True" flag to create_engine().
'NVARCHAR2' : NVARCHAR,
'CHAR' : CHAR,
'DATE' : DATE,
- 'DATETIME' : DATETIME,
'NUMBER' : NUMBER,
'BLOB' : BLOB,
'BFILE' : BFILE,
pass
colspecs = {
- sqltypes.Date : _OracleDate,
+ sqltypes.Date : _OracleDate, # generic type, assume datetime.date is desired
+ oracle.DATE: oracle.DATE, # non generic type - passthru
sqltypes.LargeBinary : _OracleBinary,
sqltypes.Boolean : oracle._OracleBoolean,
sqltypes.Interval : _OracleInterval,
(oracle.OracleRaw(), cx_oracle._OracleRaw),
(String(), String),
(VARCHAR(), VARCHAR),
+ (DATE(), DATE),
(String(50), String),
(Unicode(), Unicode),
(Text(), cx_oracle._OracleText),