[
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574335#comment-17574335
]
ASF subversion and git services commented on ISIS-3105:
-------------------------------------------------------
Commit 810e78e70111af992c13496905023d47d684ab67 in isis's branch
refs/heads/ISIS-3108 from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=810e78e701 ]
ISIS-3105: ZoneOffset.UTC and ZoneId.of("UTC") result in different
output format;
- that is 'Z' vs 'UTC'
- so we prefer to use ZoneId.of("UTC") for UTC based ZoneDateTime values
> Support for persisting Temporal Types with Zone/Offset Information
> ------------------------------------------------------------------
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
> Issue Type: New Feature
> Components: Isis Persistence JDO, Isis Persistence JPA
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA
> in support of zone/offset temporals, by adding a secondary column that holds
> the zone/offset information. Similar to what we do with Blob/Clob.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
