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 "Mamta A. Satoor (Assigned) (JIRA)" <ji...@apache.org> on 2012/03/21 02:42:39 UTC
[jira] [Assigned] (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:all-tabpanel ]
Mamta A. Satoor reassigned DERBY-5369:
--------------------------------------
Assignee: Mamta A. Satoor (was: Rick Hillegas)
> 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