Return-Path: 
 <derby-dev-return-39823-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 10290 invoked from network); 29 Mar 2007 23:45:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 29 Mar 2007 23:45:49 -0000
Received: (qmail 21570 invoked by uid 500); 29 Mar 2007 23:45:56 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 21539 invoked by uid 500); 29 Mar 2007 23:45:56 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 21528 invoked by uid 99); 29 Mar 2007 23:45:56 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2007 16:45:56 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2007 16:45:47 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 4A8EC714065
	for <derby-dev@db.apache.org>; Thu, 29 Mar 2007 16:45:25 -0700 (PDT)
Message-ID: <2028891.1175211925301.JavaMail.jira@brutus>
Date: Thu, 29 Mar 2007 16:45:25 -0700 (PDT)
From: "A B (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2500) Assertion failure preparing query with
 AND and OR in where clause
In-Reply-To: <18585362.1175124745138.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

A B updated DERBY-2500:
-----------------------

    Attachment: d2500_v2.patch

Realized after I uploaded the patch that the comments for the test case in DistinctTest need to be updated to reflect the changes made in this issue.  Other than this change to the comments, v1 and v2 are identical.

> Assertion failure preparing query with AND and OR in where clause
> -----------------------------------------------------------------
>
>                 Key: DERBY-2500
>                 URL: https://issues.apache.org/jira/browse/DERBY-2500
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Andrew McIntyre
>         Assigned To: A B
>         Attachments: d2500_v1.patch, d2500_v1.stat, d2500_v2.patch
>
>
> See commented out test in DistinctTest, DistinctTest.testResultSetInOrderWhenUsingIndex.
> The actual assert is:
> ASSERT FAILED Found IN-list probing (NLR.LUSERNAME = <expr>) while generating HASH join, which should not happen.
> I was able to simplify the query a little:
> SELECT DISTINCT nb.name AS name, nb.summary AS summary FROM netbutton1 nb, netbuttonlibraryrole1 nlr, library_netbutton ln WHERE nlr.netbuttonlibrary_id = ln.netbuttonlibrary_id AND (nlr.lusername = ? OR nlr.lusername =?)
> Removing nlr.netbuttonlibrary_id = ln.netbuttonlibrary_id clause but leaving the 'nb.lname = ln.lname' in front of the AND did not reproduce the problem.

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