Re: TIMESTAMP millisecond precision

From: Mike Kienenberger (mkienen..laska.net)
Date: Wed Dec 24 2003 - 09:05:20 EST

Next message: Mike Kienenberger: "CAY-70 patches address generic issues with NotLikeIgnoreCase and adds adaptor support for custom QualifierTranslators"

Previous message: jir..bjectstyle.org: "[OS-JIRA] Created: (CAY-71) Default OpenBase TIMESTAMP type should be timestamp, not datetime"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Andrus Adamchik wrote:
> Indeed, changing it to timestamp now allows millisecond preceison.
Interestingly that both Oracle and
> MySQL fail tests when I set milliseconds field of the test calendar....

Actually, one of the problems I encountered when I upgraded my WebObjects
application from Oracle 8 to Oracle 9 was that TIMESTAMP had changed to
provide nanosecond? accuracy, breaking all of my WebObjects optimistic date
locking (which required accuracy to be rounded to the nearest second).

I'm guessing you're doing your testing with Oracle 8.

I think I have access to a development Oracle 9 database if you'd like to
run the tests against it in the new year.

-Mike

Next message: Mike Kienenberger: "CAY-70 patches address generic issues with NotLikeIgnoreCase and adds adaptor support for custom QualifierTranslators"
Previous message: jir..bjectstyle.org: "[OS-JIRA] Created: (CAY-71) Default OpenBase TIMESTAMP type should be timestamp, not datetime"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Wed Dec 24 2003 - 09:05:00 EST