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 "Brett Bergquist (JIRA)" <ji...@apache.org> on 2011/08/02 16:43:27 UTC

[jira] [Updated] (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 ]

Brett Bergquist updated DERBY-5369:
-----------------------------------

    Attachment: derby-5369.diff

Patch to add in support for passing NOT EQUALS restriction to initScan

> 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