Jim van Keulen wrote:
hyc@symas.com wrote:
The filter behavior you're describing was noted in ITS#5756, fixed
in January.
If it was fixed in January, why does openldap-2.4.16 (20090411) still exhibit the described behaviour?
I don't believe what you're seeing now is due to the situation Ando described.
But he said that reversing the order of the filters (i.e. no objectClass=someclass first) cures the problem.
p.