We're updating the issue view to help you get more done. 

Add dedicated default value bridges for java.sql.Timestamp, java.sql.Date and java.sql.Time

Description

From the javadoc of Timestamp:

1 2 3 4 5 6 7 8 * Due to the differences between the <code>Timestamp</code> class * and the <code>java.util.Date</code> * class mentioned above, it is recommended that code not view * <code>Timestamp</code> values generically as an instance of * <code>java.util.Date</code>. The * inheritance relationship between <code>Timestamp</code> * and <code>java.util.Date</code> really * denotes implementation inheritance, and not type inheritance.

Complying applications will use Time and Timestamp in their entities instead of java.util.Date, so we'd better support that.

Also, judging from the presence of a java.sql.Timestamp#toLocalDateTime method, a java.sql.Date#toLocalDateTime method and a java.sql.Time#toLocalTime method, these classes should be converted to a LocalDateTime, LocalDateTime and LocalTime, respectively. So just using the same bridge as java.util.Date will not work.

Environment

None

Status

Assignee

Fabio Massimo Ercoli

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Priority

Major