fwiw,
for JDBC.next i am looking at adding support for time and timestamp with TZ.
-lance
Daniel John Debrunner (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523890 ]
Daniel John Debrunner commented on DERBY-2235:
----------------------------------------------
Ken> ... if a timezone-less string ordinarily defaults to GMT. Or is a tz-less
string defaults to the system's tz ...
It's neither. Derby's TIMESTAMP values are TIMESTAMP with no associated timezone information.
For information on how the datetime values interact with JDBC see:
http://db.apache.org/derby/docs/10.3/publishedapi/jdbc3/org/apache/derby/jdbc/package-summary.html
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.
