[
https://issues.apache.org/jira/browse/DERBY-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847492#comment-13847492
]
Rick Hillegas commented on DERBY-6036:
--------------------------------------
Hi Richard,
These are all interesting suggestions for improving the api for table
functions. I think this discussion deserves its own, separate JIRA.
I understand your comments about the tedium of declaring table functions. Much
of this tedium may be addressed by the optional foreignViews tool introduced in
release 10.10.1:
http://db.apache.org/derby/docs/10.10/tools/rtoolsoptforeignviews.html
If you're interested in contributing to Derby, a good place to start is here:
http://db.apache.org/derby/derby_comm.html. Once you subscribe to the derby-dev
mailing list, the community can guide you through the process.
Welcome!
-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)
