I agree - this doesn't look an Oracle problem to me. Much more likely you're using the wrong type in your code - use timestamp rather than date.
> -----Original Message----- > From: Ilia Iourovitski [mailto:[EMAIL PROTECTED]] > Sent: 03 August 2001 23:51 > To: [EMAIL PROTECTED] > Subject: Re: [castor-dev] oracle date whackiness > > > Another solution is to try to use java.sql.TIMESTAMP. > If you specify sql type of the field as timestamp castor "may" convert it. > > Ilia > > -----Original Message----- > From: Ryan Campbell [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 03, 2001 3:19 PM > To: [EMAIL PROTECTED] > Subject: Re: [castor-dev] oracle date whackiness > > > Well, your *default* date format is hard-coded at the oracle level whether > you like it or not. I'm just saying that you can change that default. > > Ryan > > -----Original Message----- > From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] > > Are we suggesting here that the date format can be hard coded at the > oracle level and that'll be ok? I would've thought that if you do date > > $1 and set the param as a date type it would be ok, but I'm pretty > green so this may not be the case with castor... its the way it would work > with a prepared statement though, which is what we're really after yes? > > cheers > dim > > On Wed, 3 Oct 2001, Ryan Campbell wrote: > > > How about a solution that doesn't involve castor? If you don't have any > > other apps running on that oracle instance, you could just set the > > nls_date_format (in your $ORACLE_HOME/dbs/initSID.ora file) to your > required > > format. Of course if other applications rely on the date being > in the old > > oracle default, you can't do this. > > > > Ryan > > > > -----Original Message----- > > From: Matthew Baird [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, October 03, 2001 1:32 PM > > To: [EMAIL PROTECTED] > > Subject: [castor-dev] oracle date whackiness > > > > > > hey Guys, > > > > I'm trying to use some date comparisons in both oracle and sql server, > very > > vanilla WHERE DATE > SOMEDATE kinda stuff. I need precision down to the > > second. in SQL Server it works great. In oracle the default is DAY level > of > > precision, unless I do the following > > > > where DATE > to_date('1999-02-01 00:00:00','YYYY-MM-DD HH24:MI:SS'); > > > > is there anyway to tell Castor to do this? Should it do this > automatically > > for oracle? > > > > thanks, > > Matthew > > > > ----------------------------------------------------------- > > If you wish to unsubscribe from this mailing, send mail to > > [EMAIL PROTECTED] with a subject of: > > unsubscribe castor-dev > > > > ----------------------------------------------------------- > > If you wish to unsubscribe from this mailing, send mail to > > [EMAIL PROTECTED] with a subject of: > > unsubscribe castor-dev > > > > > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
