Oracle sub-second timestamp handling broken in 0.3.6 et seq

Sometime after 0.3.4, modifications to the type system caused the set_input_sizes() call for Oracle execution contexts to map OracleTimestamp columns to the underlying type datetime.datetime instead of the (correct) cx_Oracle.TIMESTAMP for the call to the setinputsizes() method of the cx_Oracle cursor. As a result, any sub-seconds portion of the timestamp were stripped off on e.g. insert().

It appears that the mapping error can be corrected by having the sqlalchemy.databases.oracle.OracleTimestamp object subclass sqlalchemy.types.TIMESTAMP instead of sqlalchemy.types.DateTime. I've attached a patch against rev 2727 that does this.

Comments (2)