[
https://issues.apache.org/jira/browse/DERBY-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234464#comment-13234464
]
Kathey Marsden commented on DERBY-5369:
---------------------------------------
Regarding the doc change, was their a behavior change in this issue? If so, it
probably isn't good for backport. If not, it would be fine I think to backport
just the code changes and not worry about the doc. Users can consult the 10.8
doc if they need further clarification and typically people picking up fixes on
the branches don't rebuild the doc anyway so wouldn't benefit.
> 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
