[
https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523876
]
Ken Johanson commented on DERBY-2235:
-------------------------------------
I should clarify (though it may already be obvious to some folks) that this
issue applies to any datetime type, not just the 'timestamp' type that I
mentioned.
Also I should have stated:
In otherwords it should store the '2007-01-03 04:13:43.006' value, PLUS 8
hours, if a timezone-less string ordinarily defaults to GMT
not
"In otherwords it should store the '2007-01-03 04:13:43.006' value, minus 8
hours, if a timezone-less string ordinarily defaults to GMT"
> 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: 10.2.2.0
> 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.
