[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574111#comment-17574111 ] 

ASF subversion and git services commented on ISIS-3105:
-------------------------------------------------------

Commit 2b21b46999f85a83703c9d42dbba55161888ba86 in isis's branch refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=2b21b46999 ]

ISIS-3105: minor: some code formatting

> 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)