64d6e4d2_abase_Interface__Documentation__Python_Type
[SQL Type] SQL.TIMESTAMP [Comments] While you should use DateTime instances, the module also accepts Python datetime.datetime instances, datetime.date instances (the time part is then set to 00:00:00), ticks (Python numbers indicating the number of seconds since the epoch; these are converted to local time and then stored in the database) and tuples (year,month,day, hour,minute,second) on input. Seconds are rounded according to the setting of the .timestampresolution setting, which defines the resolution of the timestamps in nanoseconds. mxODBC will round the timestamp's second value to the nearest nanosecond fraction defined by this setting in order to avoid issues with float second values which sometimes cannot be represented with full accuracy. If not set, the .timestampresolution attribute defaults to 1 nanosecond, so rounding usually is done to the nearest nanosecond, which is also the smallest fraction supported by the ODBC standard. [Python Type] 
DateTime instance or datetime.datetime instance or datetime.date instance or a tuple (year,month,day, hour,minute,second) or String/Unicode or a ticks value as Python number
eGenix.com: Products: Python: mxODBC - Python ODBC Database Interface: Documentation
Python Type