[DERBY-3856] difference between Embedded vs DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.3.1, 10.4.2.0, 10.5.1.1
• Fix Version/s: 10.5.3.1, 10.6.2.1, 10.7.1.1
• Component/s: SQL
• Urgency: Normal
• Bug behavior facts: Deviation from standard, Embedded/Client difference
• Assignee: Knut Anders Hatlen
• Reporter: Myrna van Lunteren
• Created: 26/Aug/08 19:11
• Updated: 13/Jan/11 21:23
• Resolved: 12/Jul/10 18:12

Description

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.

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is required by: DERBY-4728 10.5 backport effort tracking issue