Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <15136572.2221275920741022.JavaMail.jira@thor>
Date: Mon, 7 Jun 2010 10:25:41 -0400 (EDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3856) difference between Embedded vs
 DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))
In-Reply-To: <1194004102.1219777964325.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876253#action_12876253 ] 

Knut Anders Hatlen commented on DERBY-3856:
-------------------------------------------

Same problem can be seen with the DATE function. Example output from the embedded driver:

ij> values date('10/07/2008');
1         
----------
2008-10-07

1 row selected
ij> values date(cast('10/07/2008' as varchar(32)));
1         
----------
10/07/2008

1 row selected

Client driver returns 2008-10-07 for both.

The TIME function does not appear to have this problem. With the embedded driver:

ij> values time(cast('10.00.00' as varchar(32)));
1       
--------
10:00:00

1 row selected

Notice that the time string is normalized (dots turned into colons).

> difference between Embedded vs DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3856
>                 URL: https://issues.apache.org/jira/browse/DERBY-3856
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.3.1, 10.4.2.0, 10.5.1.1
>            Reporter: Myrna van Lunteren
>
> There is a slight difference in how Embedded vs. DerbyNetClient return a specific cast.
> This showed up during conversion of the test lang/datetime.sql which before was only run with Embedded...
> The following sql: 
> prepare dateTimePS as 'values( date(cast(? as integer)),timestamp(cast(? as varchar(32))))';
> execute dateTimePS using 'values(cast(1 as integer), ''2003-03-05-17.05.43.111111'')';
> gives:
>                                1         |2                         
>                                -------------------------------------
> Embedded:         1970-01-01|2003-03-05-17.05.43.111111
> DerbyNetClient:  1970-01-01|2003-03-05 17:05:43.111111
> (in Embedded there's a '-' between date and time part, with DerbyNetClient a space; with Embedded the separator between time elements is ., with DerbyNetClient :. Embedded reflects the data as passed in, with DerbyNetClient it seems to be the default timestamp format).
> I am not sure which is correct at this point, but I confirmed the behavior is like this in latest builds of trunk and 10.3 and 10.4 branches.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.