db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Tarr (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4611) Add new datatypes: TIME WITH TIMEZONE and TIMESTAMP WITH TIMEZONE
Date Wed, 15 Dec 2010 11:59:03 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971652#action_12971652
] 

Greg Tarr commented on DERBY-4611:
----------------------------------

Is there an ETA on timezone support is going to be available in Derby? In particular it would
be nice to have the equivalent of Oracle's timestamp with timezone and associated support
functions.

> Add new datatypes: TIME WITH TIMEZONE and TIMESTAMP WITH TIMEZONE
> -----------------------------------------------------------------
>
>                 Key: DERBY-4611
>                 URL: https://issues.apache.org/jira/browse/DERBY-4611
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>
> The SQL Standard defines two timezone-stamped datatypes: TIME WITH TIMEZONE and TIMESTAMP
WITH TIMEZONE. Relevant sections in part 2 of the Standard include 4.6 (Datetimes and intervals),
6.1 (<data type>), 6.12 (<cast specification>), and 8.2 (<comparison predicate>).
> I think that we could implement these two datatypes today. Note that there is a general
cleanup of the Java datetime classes underway in JSR 310 ( https://jsr-310.dev.java net/ ),
which is supposed to be delivered in Java 7. It's possible that the next rev of JDBC will
provide better support for these datatypes. However, there is currently no JSR covering the
next JDBC increment. 
> For the moment, the existing JDBC TIME and TIMESTAMP types would have to be overloaded
to cover the new datatypes. Disambiguating the WITH TIMEZONE variants might have to be accomplished
by parsing the type names returned by ResultSetMetaData.getColumnTypeName() and DatabaseMetaData.getColumns().TYPE_NAME.
> Note also that DRDA does not provide WITH TIMEZONE variants of its TIME and TIMEZONE
types. Some creativity would be required here too.
> Users are welcome to vote for this issue in order to boost its chance of being addressed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message