db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5369) Restricted Table Function support should pass NOT EQUAL restrictions to initScan
Date Wed, 21 Mar 2012 16:21:41 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234465#comment-13234465
] 

Mamta A. Satoor commented on DERBY-5369:
----------------------------------------

Thanks Kathey, I will continue backporting the code changes to 10.6 and 10.5 codelines in
the meantime
                
> 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.7.1.4, 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

        

Mime
View raw message