[
https://issues.apache.org/jira/browse/DERBY-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6036:
---------------------------------
Bug behavior facts: Performance,Seen in production (was: Performance)
Hi Richard,
Thanks for your detailed description of how this problem affects your
production app. I have marked the issue as "Seen in production." That will
boost its urgency slightly. Voting for the issue will boost its urgency too.
One workaround would be to define a family of table functions and views for
each table, one table function/view for each SELECT list. Then use those views
in your queries. Unfortunately, that would involve changing the queries in your
app.
Thanks,
-Rick
> If you wrap a SELECT * view around a table, all of the columns are read from
> the base row even when you SELECT only a subset of the view columns.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6036
> URL: https://issues.apache.org/jira/browse/DERBY-6036
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Labels: derby_triage10_11
> Attachments: derby-6036-01-aa-testForRestrictionPushing.diff,
> derby-6036.sql, derbyAST.xml
>
>
> This also affects SELECTs from views wrapping RestrictedVTIs. 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 was sent by Atlassian JIRA
(v6.1.4#6159)
