On 10/19/05, Elias Torres <[EMAIL PROTECTED]> wrote: > On 10/19/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > > okay ... i've tested this and it works on mysql 4.1.x, but not on mysql > > 4.0.x. i don't think we should drop support for mysql 4.0.x, especially > > because we use a 4.0.x db for one of our roller installs here at Sun. > > > > Elias, > > > > what exactly is broken about it? does Derby/DB2/others not have a column > > type of DATETIME? or does the conversion now work from TIMESTAMP to > > DATETIME? > > > > -- Allen > > Derby/DB2 do no have a column type DATETIME, only TIMESTAMP. :-( > > I've checked for Oracle
Agreed. They have DATE and TIMESTAMP(n) afaik. > PostgreSQL This does have DATETIME, in that createdb doesn't blow up for me; but it seems to be timezoneless and has the problem I posted about. I can confirm that switching back to TIMESTAMP from DATETIME fixes the problem in Postgres. Hen
