db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3946) Provide support for using the Derby parser to generate Abstract Syntax Trees
Date Thu, 13 Nov 2008 12:31:47 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647269#action_12647269

Knut Anders Hatlen commented on DERBY-3946:

Dag, this is because the initialization of NewInvocationNode (invoked by the parser -- see
vtiTableConstruct() in sqlgrammar.jj) looks up the class name associated with the table function
in the data dictionary. That sounds like the wrong place to do it, it should probably be moved
from init() to bindExpression(). The actual verification that the class exists is (correctly)
done in bindExpression(). I wouldn't be surprised if there's more misplaced code, since until
now it hasn't really made any difference if some of the binding has been performed in the

> Provide support for using the Derby parser to generate Abstract Syntax Trees
> ----------------------------------------------------------------------------
>                 Key: DERBY-3946
>                 URL: https://issues.apache.org/jira/browse/DERBY-3946
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
>             Fix For:
>         Attachments: ASTParser.java, derby-3946-01-aa-standaloneParser.diff
> Users would like to be able to use the Derby parser to produce query trees without actually
running the queries on Derby.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message