On 10/19/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > I'm generally confused on this issue. Isn't this the kind of thing > that should be different per database and JDBC can hide from us? Why > not have DATETIME for Mysql, TIMESTAMP for Postgres, DATE for Oracle > etc? > > In JDBC you'd just use java.sql.Timestamp, which would squeeze into > each one. Hibernate I imagine you'd use a Timestamp type or something > (I'm rusty at Hibernate nowadays :) ). > > I also think this is the reason why http://db.apache.org/ddlutils/ exists. > > Apologies for the dumb email, after a year of baby-juggling, I've > finally found time to start digging into Roller and I've not delved > into how the db side of things is working.
Digging into things. Looks pretty simple (meaning it won't be, but I'm too ignorant to know why). Why not just add a property to each of the db_...properties files for the preferred java.sql.Timestamp type? Assuming that other databases are as iffy with their TIMESTAMP support as Oracle is; it seems a good one to be dynamic on. Hen
