Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14336130.2721273577321095.JavaMail.jira@thor>
Date: Tue, 11 May 2010 07:28:41 -0400 (EDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4650) Predicates in HAVING clause should be
 pushed down to restricted VTIs
In-Reply-To: <17830981.2671273576841848.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-4650:
--------------------------------------

    Attachment: test.diff

The attached patch adds a test case to RestrictedVTITest that shows that the predicate is not pushed in the following query:

    select s_r, count(*) from table(integerList()) t group by s_r having s_r > 1

Only the rows with s_r > 1 have to be returned by the table function integerList, so pushing the predicate could be useful.

Committed the new test case to trunk with revision 943088.

> Predicates in HAVING clause should be pushed down to restricted VTIs
> --------------------------------------------------------------------
>
>                 Key: DERBY-4650
>                 URL: https://issues.apache.org/jira/browse/DERBY-4650
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: test.diff
>
>
> If you perform a query with an aggregate function against a restricted table function, the predicates in the HAVING clause are not pushed down to the table function.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.