[ http://issues.apache.org/jira/browse/TORQUE-11?page=comments#action_12415754 ]
Adrian Price commented on TORQUE-11: ------------------------------------ Agreed: MySQL TIMESTAMP most emphatically is *not* the correct mapping for JDBC TIMESTAMP. The correct mapping is JDBC TIMESTAMP -> MySQL DATETIME. This is a major issue because it breaks applications which rely on normal DATETIME nullability and behaviour; for example, my own Open Business Engine (http://obe.sourceforge.net), which I am currently attempting to convert to use Torque for DDL generation. > 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.2, 3.1.1, 3.1 > > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
