On 01/05/2011 02:10 PM, Noriko Hosoi wrote: > I might have missed something in the discussion, but even if numsubordinates > is indexed only with presence: > > # dbscan -f numsubordinates.db4 -n -r > + 3 > 1 3 4 > > the range search should return the expected result: > > $ ldapsearch [...] -b "dc=example,dc=com" > "*(&(numsubordinates=*)(numsubordinates>=1))*" numsubordinates entryid > dn: dc=example,dc=com > numsubordinates: 4 > entryid: 1 > > dn: ou=Groups,dc=example,dc=com > numsubordinates: 4 > entryid: 3 > > dn: ou=People,dc=example,dc=com > numsubordinates: 2 > entryid: 4 > Perhaps the index got corrupted then some how. I've updated the bug https://bugzilla.redhat.com/show_bug.cgi?id=667488 with some further thoughts about why db2index fails with numsubordinates. Is there any other way to recreate the index? As it stands now, it is completely broken. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
