[DERBY-591] Several builtin functions are incorrectly exposed through the JDBC escaped function syntax {fn <function_call>}

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.0.2.0, 10.1.1.0, 10.3.1.4, 10.4.1.3
• Component/s: JDBC, SQL
• Labels: derby_triage10_5_2
• Urgency: Normal
• Bug behavior facts: Deviation from standard
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 30/Sep/05 06:30
• Updated: 15/Feb/11 21:08

Description

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.

Issue Links

• is related to: DERBY-471 DatabaseMetaData.getXXXFunctions() methods return incorrect values.
• is related to: DERBY-475 Add a system function mechanism and table of functions, including a set of initial functions.