[
https://issues.apache.org/jira/browse/TORQUE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092053#comment-18092053
]
Graham Leggett commented on TORQUE-375:
---------------------------------------
Latest version of the patch.
- Includes a version bump on hsqldb to fix this bug:
https://sourceforge.net/p/hsqldb/bugs/1702/
- Updated tests that were querying {code}call '2000-01-02'{code} to instead
query {code}call CAST('2000-01-02' AS DATE){code}. A lot of the messages about
being unable to change the type were complaints that VARCHAR was being accessed
as a DATE.
- Derby seems dead in the water, updating to the latest version and java21,
everything stayed broken.
- Docs are all done, and I cut and pasted the pom file and schema file to
verify that a maven project was actually created without error.
> 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, torque8-javatime5.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]
