[
https://issues.apache.org/jira/browse/TORQUE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091421#comment-18091421
]
Graham Leggett commented on TORQUE-375:
---------------------------------------
One further thing - there are what looks like two sets of dead code in there
now.
- The DateKey that maps to the legacy java.util.Date. Is there a reason to keep
this or should it be taken out? The templates ignore this object so there seems
to be little point.
- The Platform interface contains methods to generate dates as strings in
formats understood by databases, and these seemed wrong. In the new world of
prepared statements, these don't appear to make sense any more, can I rip them
out?
> 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
>
>
> 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]
