[
https://issues.apache.org/jira/browse/DERBY-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234056#comment-13234056
]
Mamta A. Satoor commented on DERBY-5369:
----------------------------------------
The checkin for this jira touches RestrictedVTITest.java. The method changed in
that test was added as part of DERBY-5370 which has not been backported to
10.7. I will go ahead and do the m(test_11_5370)(erge without the change to
RestrictedVTITest.java I didn't see DERBY-5370 as one of the candidates for
backport.
> 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.5.3.0
> Reporter: Brett Bergquist
> Assignee: Mamta A. Satoor
> Labels: features
> Fix For: 10.8.2.3
>
> Attachments: derby-5369-01-aa-inequalityOperator.diff, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
