[ http://issues.apache.org/jira/browse/TORQUE-11?page=comments#action_12449617 ] Thomas Fischer commented on TORQUE-11: --------------------------------------
The problem is not a technical one, resolving this would need to add one line of code in the class org.apache.torque.engine.platform.PlatformMysqlImpl in the method initialize(): setSchemaDomainMapping(new Domain(SchemaType.TIMESTAMP, "DATETIME")); The problem is rather a compatibility issue. The Torque team has tried hard not to make any hidden incompatible changes between 3.2 and the next release (which is probably called 3.3), and I'd consider this change to be such an incompatibility (people might rely on the magic behaviour of the timestamp). My personal idea would be to address this issue in 4.0-dev. In the meantime, if you have problems with this, you can get the sources, make the change above, and recompile the Torque generator. > Torque Type Timestamp should be mapped to datetime in Mysql > ------------------------------------------------------------ > > Key: TORQUE-11 > URL: http://issues.apache.org/jira/browse/TORQUE-11 > Project: Torque > Issue 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]
