[
https://issues.apache.org/jira/browse/DERBY-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6036:
---------------------------------
Attachment: derbyAST.xml
The problem may be more general. If you wrap a base table in a view, it appears
that the projection is not passed through to the base table either. I am
attaching derbyAST.xml, which is the printout of parse(), bind(), and
optimize() ASTs produced by the following script when you use the XmlASTPrinter
attached to DERBY-4415. From the printout, you can see the following:
1) For the SELECT from a base table (select s_nr from t where ns_r = 3000), the
optimizer wraps the base table in a ProjectRestrict node which projects out
only two columns.
2) However, for the SELECT from a view on that base table (select s_nr from vt
where ns_r = 3000), the optimizer wraps the base table in a ProjectRestrict
node which projects out ALL four columns in the table.
> If you wrap a view around a RestrictedVTI, the projection is not pushed into
> the table function.
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-6036
> URL: https://issues.apache.org/jira/browse/DERBY-6036
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Attachments: derby-6036.sql, derbyAST.xml
>
>
> Restrictions are pushed into a restricted VTI if you wrap it in a view.
> However, projections are not. I will attach a script showing this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
