Hi,

I am currently checking a bug report
(http://nagoya.apache.org/scarab/issues/id/TRQS263). I am investigating the
accuracy of TIME columns. The problem is that saving a TIME value and
retrieving it again from an Oracle DB only has day accuracy, not second
accuracy as one would expect from the SQL type TIME.
While stepping through the code, I have come to the conclusion that this
problem might not be a oracle problem, but might also occur in other
databases. To check this, I have just committed a test case to CVS branch
TORQUE_3_1_BRANCH. Can anyone whoe does _NOT_ use oracle please check this
out and run the runtime-tests? At some point, there should be output like

testDateTime() : set date to : 27.12.04 21:02
testDateTime() : retrieved date : 27.12.04 00:00
testDateTime() : retrieved time : 27.12.04 00:00
testDateTime() : retrieved timestamp : 27.12.04 21:02
testDateTime() : Date difference (ms): 75736298
testDateTime() : Time difference (ms): 75736298
testDateTime() : Timestamp difference (ms): 0

The crucial point is whether the TimeDifference is below 1000 or not.

 Thanks a lot,

      Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org