db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3856) difference between Embedded vs DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))
Date Mon, 07 Jun 2010 22:23:13 GMT

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

Dag H. Wanvik commented on DERBY-3856:
--------------------------------------

Seems like the correct solution to treat all these cases uniformly so as to always get the
normalized version. Test appears
to cover the cases.  Verified that two fixtures throw errors without the patch: DateAndDatetimeFunctionsMore
and testDerby3856,
but work when the rest of the patch is applied.

+1 from me.



> 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
>            Assignee: Knut Anders Hatlen
>         Attachments: fix.diff
>
>
> 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.


Mime
View raw message