You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/11/23 00:37:42 UTC
[jira] Created: (DERBY-723) Escaped JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function.
Escaped JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function.
--------------------------------------------------------------------------------------
Key: DERBY-723
URL: http://issues.apache.org/jira/browse/DERBY-723
Project: Derby
Type: Bug
Components: JDBC
Versions: 10.0.2.0, 10.1.2.1
Reporter: Daniel John Debrunner
Priority: Minor
JDBC/ODBC define {fn CHAR(n)} as returning a string corresponding to the ASCII character with codepoint N.
With Derby, {fn CHAR(n)} maps to CHAR(n) which results in the value n converted to a string.
Most likely would be fixed by DERBY-591, but called out as a special case beacuse this is a valid escaped function returning the wrong information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-723) Escaped JDBC/ODBCC function CHAR(n)
incorrect maps to Derby's builtin CHAR() function.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-723:
--------------------------------
Urgency: Normal
Triaged for 10.5.3: assigne normal urgency.
> Escaped JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-723
> URL: https://issues.apache.org/jira/browse/DERBY-723
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.0.2.0, 10.1.2.1
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> JDBC/ODBC define {fn CHAR(n)} as returning a string corresponding to the ASCII character with codepoint N.
> With Derby, {fn CHAR(n)} maps to CHAR(n) which results in the value n converted to a string.
> Most likely would be fixed by DERBY-591, but called out as a special case beacuse this is a valid escaped function returning the wrong information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-723) Escaped JDBC/ODBCC function CHAR(n)
incorrect maps to Derby's builtin CHAR() function.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-723:
---------------------------------
Derby Categories: [High Value Fix]
> Escaped JDBC/ODBCC function CHAR(n) incorrect maps to Derby's builtin CHAR() function.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-723
> URL: https://issues.apache.org/jira/browse/DERBY-723
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.0.2.0, 10.1.2.1
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> JDBC/ODBC define {fn CHAR(n)} as returning a string corresponding to the ASCII character with codepoint N.
> With Derby, {fn CHAR(n)} maps to CHAR(n) which results in the value n converted to a string.
> Most likely would be fixed by DERBY-591, but called out as a special case beacuse this is a valid escaped function returning the wrong information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.