[
https://issues.apache.org/jira/browse/DERBY-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4621.
---------------------------------------
Fix Version/s: 10.6.0.0
Resolution: Fixed
All tests ran cleanly.
Committed revision 936215.
> Invalid conversion from Timestamp to String when calling setTimestamp() with
> Calendar
> -------------------------------------------------------------------------------------
>
> Key: DERBY-4621
> URL: https://issues.apache.org/jira/browse/DERBY-4621
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.3.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.6.0.0
>
> Attachments: derby-4621.diff, TimestampToVarchar.java
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
