[
https://issues.apache.org/jira/browse/TORQUE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091587#comment-18091587
]
Graham Leggett commented on TORQUE-375:
---------------------------------------
All the getters and setters are now:
- java.time.LocalDate - DATE
- java.time.LocalTime - TIME
- java.time.LocalDateTime - TIMESTAMP
- java.time.OffsetDateTime - TIMESTAMP_WITH_TIMEZONE
- java.time.OffsetTime - TIME_WITH_TIMEZONE
So java.util.Date is effectively gone. You can still pass java.util.Date in
criterias, because I understand it is up to the underlying JDBC driver to
interpret the values and they still support the old dates, but the responses
back are all java.time across the board.
The java.time objects map exactly to the SQL objects, which I think was one of
the main pain points with the old java.util.Date and java.util.Calendar. So
much fiddly code is just gone.
Can you confirm how you got the test results above? I am testing like this:
{code}
mvn -Phsqldb,managers,beans,test clean install
{code}
> Support for java.time API
> -------------------------
>
> Key: TORQUE-375
> URL: https://issues.apache.org/jira/browse/TORQUE-375
> Project: Torque
> Issue Type: Improvement
> Affects Versions: 7.1
> Reporter: Graham Leggett
> Priority: Major
> Attachments: torque8-javatime1.patch, torque8-javatime2.patch,
> torque8-javatime3.patch, torque8-javatime4.patch
>
>
> Switch out java.util.Date, replace with the java.time API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
