It seems I have a knack for running into problems that were discussed at
length and (partially?) solved ages ago.
That said, I have a table in Oracle with a column of type DATE. It
doesn't matter whether I tell Torque this is a DATE or TIMESTAMP
column in the schema.xml, because as we all know,
Supposedly starting the JVM with -Doracle.jdbc.V8Compatible=true
fixes this:
http://wiki.apache.org/db-torque/OracleFAQ
However it didn't work for me, even after setting the Torque mapping
to TIMESTAMP. I had to change the columns from DATE to TIMESTAMP.
Raul Acevedo
http://www.cantara.co
On Thu, Nov 22, 2007 at 02:15:39AM -0500, Raul Acevedo wrote:
> Supposedly starting the JVM with -Doracle.jdbc.V8Compatible=true fixes
> this:
>
> http://wiki.apache.org/db-torque/OracleFAQ
>
> However it didn't work for me, even after setting the Torque mapping to
> TIMESTAMP. I had to change t
It doesn't change the whole JVM, it's a flag for the Oracle JDBC
driver. I was a little leery of that also, but enough Google
research seems to show that it only applies to the date/timestamp
handling, though admittedly I did not find a site that definitely
stated that.
Raul Acevedo
http
