[
https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528044
]
Bernt M. Johnsen commented on DERBY-2235:
-----------------------------------------
Brorwsing through the SQL2003 standard, I find that Dan is right. A timestamp
without timezone has no associated timezone, not even implicit. So '2000-01-01
12:00:00' in LA is '2000-01-01 12:00:00' in NY since no timezone is
associated with the datatype. Then it is the application's problem to interpret
the values. The standard *does* say, however, that the current SQL-session's
timezone is applied if timezone is required (e.g when cast to TIMESTAMP WITH
TIMEZONE). Quote from the standard:
If <time zone interval> is not specified, then no assumption is made about time
zone displacement. However, should a time zone
displacement be required during subsequent processing, the current default time
zone displacement of the SQL-session will be
applied at that time.
> 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.
