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/22 23:19:42 UTC

[jira] Commented: (DERBY-591) Several builtin functions are incorrectly exposed through the JDBC escaped function syntax {fn }

    [ http://issues.apache.org/jira/browse/DERBY-591?page=comments#action_12358311 ] 

Daniel John Debrunner commented on DERBY-591:
---------------------------------------------

These functions also incorrectly work as escaped functions. Prior to DERBY-471 being fixed they were incorrectly  listed in the various DatabaseMetaData methods that return the supported escaped functions.

values {fn LOWER('HELLO')};
values {fn SUBSTR('Bonjour', 4)};
values {fn SUBSTRING('bonjour', 4)};
values {fn UPPER('goodbye')};
values {fn CURRENT_USER() };
values {fn SESSION_USER() };

> Several builtin functions are incorrectly exposed through the JDBC escaped function syntax {fn <function_call>}
> ---------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-591
>          URL: http://issues.apache.org/jira/browse/DERBY-591
>      Project: Derby
>         Type: Bug
>     Versions: 10.0.2.0, 10.1.1.0
>     Reporter: Daniel John Debrunner
>     Priority: Minor

>
> Due to lack of direction in the way functions are added into the parser, any functions that are added into the parser's miscBuiltinsCore are also automatically JDBC/ODBC escaped functions.
> E.g. the new XML functions (e.g. XMLPARSE), COALESCE, VALUE etc. etc.
> The correct set of escaped scaler functions is defined in appendex C (C1- C5)  of JDBC 3.0.
> Discovered this while trying to make the JDBC escape functions table driven, at least for the valid subset of table driven functions added in DERBY-475.
> Probably just need to split the miscBuiltins core into two functions, one for functions that are SQL and allowed in JDBC escape, and one for ones only allowed in SQL.

-- 
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