db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2235) Server doesnt support timestamps with timezone
Date Tue, 11 Sep 2007 16:13:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526509

Daniel John Debrunner commented on DERBY-2235:

>>if the string '2007-01-03 04:13:43' is converted to a TIMESTAMP in SQL then it will
always represent '2007-01-03 04:13:43'

> In what timezone? GMT? The server's? 

No time zone,  Derby's TIMESTAMP values are TIMESTAMP with no associated timezone information.

It's just 04:13 with no associated timezone. If the server's timezone was change to something
else, the value remains at 04:13 as it is not associated with a timezone.

> Server doesnt support timestamps with timezone
> ----------------------------------------------
>                 Key: DERBY-2235
>                 URL: https://issues.apache.org/jira/browse/DERBY-2235
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Ken Johanson
>            Priority: Minor
> DML with datetime literals having timzone offset data (ISO-8601):
> update tbl set dt1 = '2007-01-03 04:13:43.006 -0800'
> Causes:
> SQLException: The syntax of the string representation of a datetime value is incorrect.
> Error: -1 SQLSTATE: 22007
> I believe that even if the storage does not (does it?) support timezone storage, the
input of a TZ could be normalized (offset applied) to the default TZ.

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

View raw message