On 10/17/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > On Sun, 2005-10-16 at 17:12, Elias Torres wrote: > > I just noticed that change in the schema (date field in weblogentry) > > too and it breaks DB2 since the field type is not supported. I checked > > documentation and datetime is also not supported on Derby either. > > Anyways, I don't know the differences between datetime and timestamp. > > Why does pubtime need to be a datetime as opposed to a timestamp? Is > > this something that can be done via a customizable datatype as in > > TEXT? Just a thought. > > I put in the change from Timestamp to Datetime because in Mysql if you insert > a NULL value into a Timestamp column then Mysql will automatically set it to > the current date/time. The modification I made to the way pubtime works > requires that we be able to save draft entries with a NULL pubtime. > > In Mysql the Timestamp and Datetime are the exact same thing except that a > Datetime will never be set automatically.
Definitely a good reason to change for MySql. Given that a java.sql.Timestamp is the relevant class in either case, how does changing this affect the other db's? Does Hibernate have separate Timestamp and Datetime mappings? Hen
