db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fischer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TORQUE-11) Torque Type Timestamp should be mapped to datetime in Mysql
Date Mon, 01 May 2006 16:44:49 GMT
    [ http://issues.apache.org/jira/browse/TORQUE-11?page=comments#action_12377244 ] 

Thomas Fischer commented on TORQUE-11:

This is problematic because of the magic behaviour of the timestamp column.

The magic behaviour happens if a mysql timestamp column is set to null, then it is automatically
set to the current date by mysql. Once this has happened, the magic behaviour is not seen
any more because the timestamp column is set explicitly on every update.

For mysql datetime columns, if the column value is set to null and saved, it is retrieved
as null again.

>  Torque Type Timestamp should be mapped to datetime in Mysql
> ------------------------------------------------------------
>          Key: TORQUE-11
>          URL: http://issues.apache.org/jira/browse/TORQUE-11
>      Project: Torque
>         Type: Improvement

>   Components: Generator, Runtime
>  Environment: Mysql
>     Reporter: Thomas Fischer
>      Fix For: 3.1, 3.1.1, 3.2

> Currently, the torque type timestamp is mapped to timestamp in mysql. However, timestamp
in mysql has a range only from 1970 to 2037, whereas datetime has a range from 1000 to 9999.
Both seem to have second precision. Thanks to Joerg Friedrich for suggesting this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message