[
https://issues.apache.org/jira/browse/DERBY-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987069#action_12987069
]
Knut Anders Hatlen commented on DERBY-4965:
-------------------------------------------
Thanks for looking at the patch. I modified some comments on the embedded side
that said the behaviour matched JCC, and added a comment saying the same on the
client side. I didn't intend to imply that JCC is supported, just have some
historical background as to why this behaviour is as it is. The behaviour of
getBoolean() (return true for "False" for example) is a bit odd, so I felt an
explanation was warranted.
> 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.
