You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/08/02 21:06:27 UTC
[jira] [Commented] (DERBY-5369) Restricted Table Function support
should pass NOT EQUAL restrictions to initScan
[ https://issues.apache.org/jira/browse/DERBY-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078370#comment-13078370 ]
Rick Hillegas commented on DERBY-5369:
--------------------------------------
Thanks for the patch, Brett. Looks good to me. Would be good to have a test case for this one too. In addition, the following documentation work needs to be done:
1) The header comment in RestrictedVTI should list != and <> as affected operators.
2) Those operators should also appear in the list of operators in the Developer's Guide section titled "Writing restricted table functions".
I will log a doc issue for (2) and link it to this issue. Someone else will probably tackle (2) so you don't need to worry about that one unless you want to learn how to evolve Derby documentation. Thanks.
> Restricted Table Function support should pass NOT EQUAL restrictions to initScan
> --------------------------------------------------------------------------------
>
> Key: DERBY-5369
> URL: https://issues.apache.org/jira/browse/DERBY-5369
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.1.2
> Reporter: Brett Bergquist
> Labels: features
> Attachments: derby-5369.diff
>
>
> Restricted Table Function support should pass NOT EQUAL restrictions to initScan. Currently any "!=" or "<>" constraints on the SQL used in the WHERE clause of a SELECT on a Restricted Table Funtion are not passed to the initScan method. These can be useful depending on how the Restricted Table Function is implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira