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://www.cantara.com
On Nov 22, 2007, at 2:28 AM, Brendan Miller wrote:
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 the columns from DATE to TIMESTAMP.
Yes, I read of that "fix". I was a little leery about changing the
whole JVM. We have other non-Torque/Village code that runs under the
JVM that may rely on the present behavior.
I was hoping to locate the Village patch I keep reading about. :)
Brendan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
