[
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.
