When I use timestamp(6) Oracle column type in 9i, Hibernate only uses tenths of a second (it appears). This is a generated query:



Is there a configuration for Hibernate (or Java if that is where the issue is, I assume its not the driver, though could be there too) where we can use a more specific timestamp? We want a trigger on our table to see if the query is updating the timestamp, and if not, set it to the current timestamp. However, since Hibernate is only to tenths of a second, successive queries are getting changed by the trigger, and then Hibernate is unhappy:



I know I could use an integer intead of timestamp for versioning, but timestamps seem more useful (as long as they work).

Thanks!
Chris

Whoops, I figured this out (thanks for not yelling about my not posting my code :) ), I think the type of the java property wasnt a Timestamp... Now it seems to be doing what I need now that it is Timestamp, so far so good. Chris

I take that back. :) Disregard my last post, I thought when I had changed my object hierarchy something happened, but it didnt.

When I debug, and stop at TimestampType.toString(), I see the timestamp has millis:

2004-08-21 17:14:30.685

However, in my DB trigger, I log the changes, and it is only getting a specificity of seconds:

old( 08/21/2004 16:55:39:000000) = new (08/21/2004 16:55:39:000000) for member id: 1229

Also, if I look at inserts from Hibernate, I see values truncated to seconds.

When I insert from SQLPlus, it works fine (and stores the millis), and the trigger works fine. The DB column type is Timestamp(6).

So now I assume this is a DB driver problem. I am using a Oracle 9i thin driver. Any ideas?

Thanks,
Chris

Sorry for so many posts. I downloaded the latest 9i Java 1.4 driver (ojdbc14.jar) from:

http://www.oracle.com/technology/softwa ... c9201.html

And now, finally, millis are going to the DB... Phew!

Thanks for listening,

Chris