db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-591) Several builtin functions are incorrectly exposed through the JDBC escaped function syntax {fn <function_call>}
Date Fri, 10 Feb 2006 10:32:57 GMT
    [ http://issues.apache.org/jira/browse/DERBY-591?page=comments#action_12365873 ] 

Bernt M. Johnsen commented on DERBY-591:

What about the functions that are allowed in JDBC but not in SQL (or have different name/syntax
in SQL)? The ones I know is:

JDBC                     SQL
{fn LENGTH(...)}         CHARACTER_LENGTH(....)
{fn SUBSTR(....)}        SUBSTRING(....)
{fn LTRIM(...)}          TRIM(....) 
{fn RTRIM(...)}          TRIM(....)
{fn LOCATE(...)}         POSITION(....)
{fn CURTIME()}           LOCALTIME

(The parameters may not have the same order/syntax/number)

> 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
>   Components: JDBC, SQL
>     Versions:,
>     Reporter: Daniel John Debrunner
>     Assignee: Satheesh Bandaram
>     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
> 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
> 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:
For more information on JIRA, see:

View raw message