[jboss-jira] [JBoss JIRA] (HIBERNATE-120) Hibernate maps type "timestamp" to Mysql's type "datetime" not "timestamp"
[
https://issues.jboss.org/browse/HIBERNATE-120?page=com.atlassian.jira.plu...
]
Omri Shaked commented on HIBERNATE-120:
---------------------------------------
I can't believe this hasn't been fixed since August 2009!!
Is this ever going to be fixed?
People are still using MySQL, you know...
Hibernate maps type "timestamp" to Mysql's type
"datetime" not "timestamp"
--------------------------------------------------------------------------
Key: HIBERNATE-120
URL: https://issues.jboss.org/browse/HIBERNATE-120
Project: Hibernate Integration
Issue Type: Bug
Reporter: zhou yanming
Assignee: Steve Ebersole
Priority: Critical
datetime will trim millisecond
record.setLastModified(new Date(1250053078708));
session.save(record);
....
record = session.load(record.getId());
System.out.println(record.getLastModified()); // here is 125005307000 not expected
1250053078708
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira