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.
Actually, at the risk of getting pelted with tomatoes... Since my work is pretty much always in Java, and Java and dates/sql date are a pain to deal with/convert sometimes, I just convert all my dates to Long(s) (time in millis) and store them in the DB as such. For Oracle I use NUMBER, for Postgres Integer etc... So when I get the data back, I don't have to do anything DB special, I just convert the date from Long to a Date String and pass it to the view, the conversion requires less steps, and is more consistent.. This also makes it very cool to calculate date diffs etc, and I find the app to be much more portable between DBs.
It might be different, and perhaps unconventional, but it's worked like a charm.
R
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
