[jira] [Comment Edited] (TORQUE-375) Support for java.time API

    [ https://issues.apache.org/jira/browse/TORQUE-375?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1809=
2023#comment-18092023 ]=20

Georg Kallidis edited comment on TORQUE-375 at 6/27/26 11:16 AM:
-----------------------------------------------------------------

Because of this, as Derby might not support java.time and is not actively m=
aintained any more, I switched to hsqldb as it seems with similar settings.

I think now, the tests are ok, because in the generates peer classes the in=
itial values should indeed be always null. Setting CURRENTDATE as default m=
akes of course only sense when a new instance is created/saved in the datab=
se, not before. That is, setting here on the instance variable the date/dat=
etime/timestamp is indeed wrong.


was (Author: gk):
Because of this, Derby might not support javs.time and is not actively main=
tained any more, I switched to hsqldb as it weems similar.=C2=A0

I think now, the tests are ok, because in the generates peer classes the in=
itial values should indeed be always null. Setting CURRENTDATE as default m=
akes of course only sense when a new instance is created/saved in the datab=
se, not before. That is, setting here on the instance variable the date/dat=
etime/timestamp is indeed wrong.

> 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, to=
rque8-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)