Joe,
I haven't posted this to the list because I'm not sure it's entirely relevant to your specific need. What I found I had to do with Oracle TIMESTAMPs to get them to correctly deal with min, hours, secs, etc. was to: A. write my own converter and B. extend the PlatformOracle9iImpl class to make sure I was calling setTIMESTAMP on a OraclePreparedStatement (in setObjectForStatement).
All this was with the vanilla rc5 release.
If you think this would help, I can post you the code. I had a post on the OJB-DEV list about this and Armin (I think) suggested I post tests and a fix. Unfortunately I haven't had time to do this.
Hoping this may help,
For what it's worth, Brad M is the one who started this thread; for now, I haven't been victim to the problem -- I was just saying that there should be an OJB way to fix it without changing the database configs (and potentially disrupting other applications which liked the database config the way it was.) I just haven't learned the OJB internals well enough to know where that goes.
It sounds like you've found that method. Maybe you can post a bug/enhancement request that at least contains your code, so that anyone who needs it might find it, and if you don't have time to flesh it out, another OJB contributor would have something to start from.
We still use Oracle 8; is your fix 9i specific, or could it go in the base Oracle platform class? Why did you have to write a custom converter?
Thanks for the info.
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]
