[
https://issues.apache.org/jira/browse/DERBY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-591:
----------------------------------
Affects Version/s: 10.3.1.4
Fix Version/s: 10.4.0.0
Assignee: Kristian Waagan
I plan to have a look at this and some related issues.
This is my first adventure in the realm of the parser, so I would be very
thankful for suggestions and feedback along the way.
The first patch will aim to fix the problem in the way described (splitting a
single method into two), and then I'll work on it to see how much more code
must be moved around or duplicated.
I have one question already.
Is it okay to clean this up properly, or do we have to keep certain things the
way they have used to be for compatibility?
Can we remove all misplaced functions from the fn-set? (for instance the XML
functions)
Can we remove all misplaced fn-functions from the SQL-set? (for instance LTRIM)
> Several builtin functions are incorrectly exposed through the JDBC escaped
> function syntax {fn <function_call>}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-591
> URL: https://issues.apache.org/jira/browse/DERBY-591
> Project: Derby
> Issue Type: Bug
> Components: JDBC, SQL
> Affects Versions: 10.0.2.0, 10.1.1.0, 10.3.1.4, 10.4.0.0
> Reporter: Daniel John Debrunner
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.4.0.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
