Timestamp columns created incorrectly

[tindzk]

Consider a table with the following two columns:

val created  = column[Timestamp]("created")
val modified = column[Timestamp]("modified")

SHOW CREATE TABLE TableName shows that the columns were created as follows:

`created` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00'

Neither of the two columns should have a default value or update the timestamp automatically.

[mkotsbak]

That is probably because of MySQL's "fun" automagic TIMESTAMP type. It is expected. Maybe it should be mapped to the less magic DATETIME type?

[darkfrog26]

@mkotsbak, the only problem I have with using DATETIME is that it requires 8 bytes instead of 4 bytes, but that's hardly a big deal and given the confusion dealing with TIMESTAMP it seems a perfectly acceptable trade-off.

[mkotsbak]

Ah, didnt know that difference. Is it for storing the timezone?

[darkfrog26]

This is a worthwhile read comparing the distinctions: http://infopotato.com/blog/index/datetime_vs_timestamp