[egenix-users] "right truncation" warning in mx.ODBC.Windows

[M.-A. Lemburg]

>>> Maybe there's some option setting that will automatically truncate
>>> fractional seconds, and I don't have it set? Can't find anything in the
>>> documentation, though. FWIW, Transact-SQL docco says """Date and time
>>> data from January 1, 1753 through December 31, 9999, to an accuracy of
>>> one three-hundredth of a second (equivalent to 3.33 milliseconds or
>>> 0.00333 seconds). Values are rounded to increments of .000, .003, or
>>> .007 seconds, as shown in the table.""", so it should be capable of
>>> sub-second resolution. Perhaps it just doesn't like values that require
>>> rounding?

Still looking for a good work-around to apply to the next
release...

Would rounding to the nearest hundreth of a second help ?
E.g. does the driver complain about values such as 0.01,
0.02, 0.03, 0.04 seconds ?

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Mar 13 2004)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
EuroPython 2004, Göteborg, Sweden                           85 days left

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::