Brad,
I do not think it is OJB/JDBC problem.
What is strange about your mail is the fact that NLS_DATE_FORMAT fixed the problem -
instead of NLS_TIMESTAMP_FORMAT. Since you
applied JavaDate2SqlTimes converter - all your dates at JDBC level should have been
converted to java.sql.Timestamp.
Please do not be confused by the way P6SPY displays generated JDBC query (it may be
approximate).
----- Original Message -----
From: "Joe Germuska" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Thursday, February 19, 2004 10:34 AM
Subject: Re: Oracle date tip
> At 8:16 AM -0700 2/19/04, Brad Matlack wrote:
> >
> >Normally, a "manual" oracle date query would look something like this:
> >A0.audit_date > TO_DATE('01-JAN-2001 00:00:00','DD-MON-YYYY HH24:MI:SS')
> >But this is not a portable query.
>
> Right -- that's what I was thinking too. I'm hoping some of the OJB
> gurus can explain to use where you'd put that in, because from
> browsing the API, it seems as if there is support for platform
> specific SQL. I just don't have time to unravel the complete path!
>
> Joe
>
> --
> Joe Germuska
> [EMAIL PROTECTED]
> http://blog.germuska.com
> "Imagine if every Thursday your shoes exploded if you tied them
> the usual way. This happens to us all the time with computers, and
> nobody thinks of complaining."
> -- Jef Raskin
>
> ---------------------------------------------------------------------
> 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]
