db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (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 13:35:44 GMT

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

Rick Hillegas commented on DERBY-3946:

I agree with Knut's analysis. The parse-time constructor for NewInvocationNode contains a
bind-time call to the data dictionary. I regard this as a bug. The bug could probably be fixed
by faulting in the metadata only when it is needed rather than pro-actively reading the catalogs
when the AST is created.

I also agree with Knut that the devil is in the details. Since a standalone parser hasn't
been tested widely, there are likely to be several cases where bind-time logic has leaked
into the parsing phase. Again, as they come up, I think we should clean them up. It might
be worth figuring out how we could record all of the SQL that is issued by our regression
tests and then pump that SQL through the ASTParser logic. That could give us some confidence
that we have found the central bulge of problems--though it would not be a systematic way
to catch all of the outliers.

> 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