> > Oracle doesn't have a TIMESTAMP type; its "DATE" encompasses SQL TIME,> TIMESTAMP, and DATE.
No I think you misunderstood the meaning of TIMESTAMP with Oracle in this case. With MySQL for example Timestamp column is just that a timestamp from the DB, nothing you can insert into, like an auto date column. In Oracle timestamp contains the date AND time in the field, where as the date field contains just the date.
I may well have... I always figured that since you can't make a column in an Oracle table of type "timestamp" that it was just an Oracle quirk. Or, to avoid sticking my neck out too far again, whenever I tried using "timestamp" as a column type in my Oracle databases, I've gotten an error.
In any case, it seems like everyone who is used to writing Oracle SQL is used to using the "to_date" function to make sure that their String representations use correct date formats, and it seems like one shouldn't have to change a database-level setting to make OJB work. There should be an application-layer place to make it work.
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]
