[DERBY-4621] Invalid conversion from Timestamp to String when calling setTimestamp() with Calendar

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.3.0
• Fix Version/s: 10.5.3.1, 10.6.1.0
• Component/s: SQL
• Issue & fix info: Repro attached
• Bug behavior facts: Wrong query result
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 20/Apr/10 13:33
• Updated: 13/Jan/11 17:18
• Resolved: 09/Jul/10 17:42

Description

If you set a VARCHAR parameter with setTimestamp(), the string will be formatted differently depending on whether a Calendar is specified or not, even if the default calendar is used.

Take for example this statement:

VALUES CAST(? AS VARCHAR(30))

I executed this statement twice with the same Timestamp instance. First like this:

ps.setTimestamp(1, ts);

and then like this

ps.setTimestamp(1, ts, Calendar.getInstance());

In this example, both of the methods should use the default Calendar to convert the timestamp to a string. However, I see that they generate different strings:

2010-04-20 15:17:36.0 vs 2010-04-20 03:17:36

Note there are two differences:

1) The method that takes a Calendar object does not show the fraction part (.0)

2) The method that takes a Calendar object is 12 hours off (03 instead of 15)

Issue Links

• blocks: DERBY-4582 Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only).
• is required by: DERBY-4728 10.5 backport effort tracking issue