db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3856) difference between Embedded vs DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))
Date Tue, 26 Aug 2008 19:12:44 GMT
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
    Affects Versions: 10.3.3.1, 10.4.2.0, 10.5.0.0
            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).

I am not sure which is correct at this point, but I confirmed this is the same 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.


Mime
View raw message