[
https://issues.apache.org/jira/browse/DERBY-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987022#action_12987022
]
Dag H. Wanvik commented on DERBY-4965:
--------------------------------------
Looks good to me, +1. One question, you added a comment implying that JCC is
still supported with Derby. I thought that was no longer the case? I can no
longer find the mail I thought I saw fly by on this though..
> Boolean to char conversion results in integer
> ---------------------------------------------
>
> Key: DERBY-4965
> URL: https://issues.apache.org/jira/browse/DERBY-4965
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.7.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.8.0.0
>
> Attachments: derby-4965-1a.diff, derby-4965-1b.diff,
> derby-4965-1c.diff, update-comments.diff
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Seen when running the Java EE CTS on Derby 10.7.1.1. The following code
> results in "1" being printed, whereas the expected result is "true":
> PreparedStatement ps = c.prepareStatement("values cast(? as
> char(10))");
> ps.setObject(1, Boolean.TRUE, Types.CHAR);
> ResultSet rs = ps.executeQuery();
> rs.next();
> System.out.println(rs.getString(1));
> Same seen when using VARCHAR or LONGVARCHAR instead of CHAR, and when using
> setBoolean() instead of setObject().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
