db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (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 14:54:59 GMT
    [ http://issues.apache.org/jira/browse/DERBY-591?page=comments#action_12365900 ] 

Daniel John Debrunner commented on DERBY-591:

Not sure what you are asking here Bernt. This is a bug reporting that several Derby functions
are incorrectly exposed thorugh the JDBC escaped function mechanism.   It's not about implementing
more escaped functions.

If you were concerned that a patch might break the set of functions you listed then I've already
added tests in jdbcapi/metadata.java that see which of the standard escaped functions are
implemented by Derby and which are declared to be implemented by Derby. And that those match.

I have reported also DERB-723 where  {fn CHAR(...)} is being incorrectly mapped to CHAR(....).

> 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