#47872 Filter AND with only one clause should be optimized
Closed: wontfix None Opened 7 years ago by nhosoi.

Description of problem:

if a filter is specified as (&(x=y)) instead of (x=y), this could provoke a
certain degradation in cases filter is evaluated for large number of
attributes.

The workaround is obvious: use a well designed filter.


Ludwig, thank you for taking care of this issue!

master:
commit 29316b1
Author: Ludwig Krispenz lkrispen@redhat.com
Date: Thu Aug 14 12:35:40 2014 +0200
Ticket 47872 - Filter AND with only one clause should be optimized

389-ds-base-1.3.2:
56d8a5b..39adbdc 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 39adbdc

389-ds-base-1.2.11:
5e6bee9..a791bff 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit a791bff

Metadata Update from @nhosoi:
- Issue assigned to lkrispen
- Issue set to the milestone: 1.2.11.30

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1203

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

a year ago

Login to comment on this ticket.

Metadata