Re: Storing time values via jdbc thin driver

From: Chris Seidel <>
Date: Sun, 30 Nov 2008 22:33:32 +0100
Message-ID: <493306ad$0$31861$>

Vladimir M. Zakharychev wrote:

> Answering OP's question: this is a known behavior change between 8i/9i
> and 10g JDBC drivers, documented in the Metalink note 269517.1 and bug
> #3038799. If you are sure you will stick to 10g driver, just update
> all rows so that the date component is Jan 1, 1970, I think this
> should do the trick. If you are going to use different driver
> versions, either stop using literals and start using binds with
> properly initialized date component (the note recommends to always
> initialize a Calendar object to Jan 1st, 1970 and then instantiate
> java.sql.Time from it) or choose a different data type (INTERVAL DAY
> TO SECOND, for example.)

Thank you very much for the detailed explanation! Received on Sun Nov 30 2008 - 15:33:32 CST

Original text of this message