[
https://issues.apache.org/jira/browse/DERBY-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801054#comment-13801054
]
Rick Hillegas commented on DERBY-6385:
--------------------------------------
Linking to DERBY-590 since this approach may be useful if we want to load and
unload optional Lucene-specific language.
> Make it possible to plug alternative parsers into Derby.
> --------------------------------------------------------
>
> Key: DERBY-6385
> URL: https://issues.apache.org/jira/browse/DERBY-6385
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Attachments: plugableParser.diff
>
>
> It would be nice to be able to plug alternative parsers into Derby. In
> particular, it would be useful to be able to declare a list of parsers which
> Derby could walk through, looking for one which could digest a SQL statement.
> This, in turn, could be useful for optional tools which need to load/unload
> optional language into/from the parser. When you load the optional tool, it
> could add its parser to the end of the list. When you unload the optional
> tool, it could remove its parser from the list.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
