db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4965) Boolean to char conversion results in integer
Date Fri, 08 Apr 2011 13:08:06 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-4965:
---------------------------------

    Attachment: releaseNote.html

Attaching a new version of the release note. This version does not have the blockquotes which
violate the WCAG accessibility guidelines at http://www.w3.org/TR/WCAG10/

> 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.1.0
>
>         Attachments: derby-4965-1a.diff, derby-4965-1b.diff, derby-4965-1c.diff, releaseNote.html,
releaseNote.html, releaseNote.html, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message