Hibernate version: 2.1.8

Has anybody already experienced strange behaviour with Date fields using Hibernate 2.1.8 under Oracle 9i ?

I'm currently migrating from Oracle 8i to Oracle 9i and criteria based upon java.util.Date fields doesn't work anymore.

Yann

What happens when it doesnt work? Stacktrace? Code? Etc? also, the type coming back from the DB might be a sql.Timestamp which is subclass of util.Date... Chris

Select by Criteria on Date field doesn't work anymore.

My test case is :

- Select an existing Evenement Object by Date Field And Id






EXISTING_DATE_CREATION is the exact same java.util.Date object used for the creation of the Evenement Object that I try to select.

And select is always blank...

I have seen problems concerning handling of java.sql.timeStamp and TIMESTAMP sql type in Oracle 9i but It doesn't seem to apply to me as I use java.util.Date for Hibernate Mapping and DATE for the sql column type

Hello Yann

This issue is closely related to the one I discussed recently in Sun's JDBC forum (http://forum.java.sun.com/thread.jspa?forumID=48&threadID=629746)

Essentially you need to convert the java.util.Date you are using to the same resolution as the datatype in Oracle (e.g. seconds for date).

In the same vein as your example above, we have:

// convert mills to seconds using integer arithmetic kludge
java.util.Date myModifiedDate =
new Date(((myOriginalDate.getTime()/1000)*1000));

lookupCriteria.add(Expression.eq("mydatefield", myModifiedDate));
List results=lookupCriteria.list();
System.out.println("results size: "+results.size()); // prints 1

Note that the way the Oracle drivers convert a java.util.Date for storage is not documented. I've always assumed they truncate rather than rounding, which is why I use the conversion method above. It appears to work but YMMV.

Regards

Jonathan.

I take it in the hibernate config file you have select Oracle9I dialect and not the Oracle dialect?? If you haven't then do so and this should fix the problem - I was having a similar prob but in trying to convert from 9i to 8i. Ummm if you are already using the 9i dialect then forgive me for intruding!

s

Problems seems to be solved by using Oracle 8i jdbc drivers ?????

No I meant - make sure you ARE using the Oracle9i dialect - and not the Oracle dialect (which is pre 9i version) - sorry I got my words muddled!!

S :)

In my previous post, I meant that my problem was actually solved by replacing jdbc drivers with Oracle 8i drivers ;-)

OK - weird!! All I know is that when I looked at the hibernate source code for the different dialect classes is that there is an explicit workaround for the problem of converting between date types between 8i and 9i. How strange for you then?? So which dialect are you using now?? And the driver is 8 ey ... oh well if it is working what can I say??! :)

Oracle 9i Dialect + Driver Jdbc Oracle 8i

Weird, but validated with 640 JUnit test cases ...