Jacopo, I have a fix prepared that I'm testing right now. It's the change I mentioned last week - I'm taking the conversion framework out of the entity engine, so this problem will go away.
I've tested it on a few databases, but not Oracle. So when you see the commit, please test it with Oracle and let me know how it works. -Adrian --- On Tue, 6/29/10, Jacopo Cappellato <[email protected]> wrote: > From: Jacopo Cappellato <[email protected]> > Subject: Re: svn commit: r952997 - > /ofbiz/trunk/framework/base/src/org/ofbiz/base/conversion/DateTimeConverters.java > To: [email protected] > Date: Tuesday, June 29, 2010, 10:54 PM > > On Jun 29, 2010, at 6:45 PM, Adrian Crum wrote: > > > > I think I found out the real reason there is a problem > with Oracle. In JDBC there are three date/time SQL types: > Date, Time, and Timestamp. Oracle has only two date/time SQL > types: DATE and TIMESTAMP. Oracle does not have a TIME SQL > type. > > > > The fieldtypeoracle.xml file contains this: > > > > <field-type-def type="date-time" > sql-type="TIMESTAMP" sql-type-alias="TIMESTAMP(6)" > java-type="java.sql.Timestamp"></field-type-def> > > <field-type-def type="date" sql-type="DATE" > java-type="java.sql.Date"></field-type-def> > > <field-type-def type="time" sql-type="DATE" > java-type="java.sql.Time"></field-type-def> > > > > So, I assume the Oracle JDBC driver is returning a > java.sql.Date type for the OFBiz "time" data type. > > > > -Adrian > > Should I try with the following setting: > > > <field-type-def type="time" sql-type="DATE" > java-type="java.sql.Date"></field-type-def> > > ? > > I think I will be able to d this test if you want me to try > it. > > Kind regards, > > Jacopo > >
