[
https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-2235:
-----------------------------------------
Issue Type: Improvement (was: Bug)
This would be an improvement, not a bug, though I'm not sure what TIMESTAMP
value should be inserted here.
Derby's TIMESTAMP values are TIMESTAMP with no associated timezone information.
In the above example, would the timestamp inserted be:
2007-01-03 04:13:43.006 (local time in -0800 timezone)
2007-01-03 12:13:43.006 (GMT time)
2007-01-03 XX:YY:43.006 (conversion from -0800 to the server jvm's local 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.
