db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Acevedo <r...@cantara.com>
Subject Re: Oracle Date Village Patch
Date Thu, 22 Nov 2007 07:15:39 GMT
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.com

On Nov 22, 2007, at 2:08 AM, Brendan Miller wrote:

>
> 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, Village uses this
> crazy ResultSetMetaData business.  (SELECT * FROM TABLENAME WHERE 1  
> = -1 !!!)
>
> So I read of several places where there is a Village patch that makes
> re-interprets Oracle's reporting of DATE types to be Timestamps or
> somesuch.  Bascially, something so that when I have a java.util.Date
> field in one of my table objects, I can setField(new Date()) and have
> the database show hours/minutes/seconds.
>
> Where is this code?  Or what is the workaround?  I do not have the
> freedom of altering the existing table to use timestamp types.
>
> Brendan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message