Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 30 Aug 2007 13:44:47 -0400
From: "Lance J. Andersen" <Lance.Andersen@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-2235) Server doesnt support timestamps
 with timezone
In-reply-to: <6984243.1188495631420.JavaMail.jira@brutus>
Sender: Lance.Andersen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <46D7020F.9070700@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_gbKqoTDL3EQuzmKOQET3nQ)"
References: <6984243.1188495631420.JavaMail.jira@brutus>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)

This is a multi-part message in MIME format.

--Boundary_(ID_gbKqoTDL3EQuzmKOQET3nQ)
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT

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.
>>     
>
>   

--Boundary_(ID_gbKqoTDL3EQuzmKOQET3nQ)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
fwiw,<br>
<br>
for JDBC.next i am looking at adding support for time and timestamp
with TZ.<br>
<br>
-lance<br>
<br>
Daniel John Debrunner (JIRA) wrote:
<blockquote cite="mid:6984243.1188495631420.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">    [ <a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523890">https://issues.apache.org/jira/browse/DERBY-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523890</a> ] 

Daniel John Debrunner commented on DERBY-2235:
----------------------------------------------

Ken&gt;  ... 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:

 <a class="moz-txt-link-freetext" href="http://db.apache.org/derby/docs/10.3/publishedapi/jdbc3/org/apache/derby/jdbc/package-summary.html">http://db.apache.org/derby/docs/10.3/publishedapi/jdbc3/org/apache/derby/jdbc/package-summary.html</a>


  </pre>
  <blockquote type="cite">
    <pre wrap="">Server doesnt support timestamps with timezone
----------------------------------------------

                Key: DERBY-2235
                URL: <a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/DERBY-2235">https://issues.apache.org/jira/browse/DERBY-2235</a>
            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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--Boundary_(ID_gbKqoTDL3EQuzmKOQET3nQ)--