RE: Trouble found: substring searches very broken (ITS#402)

[hyc@highlandsun.com]

But all in all it would be best to fix the broken ID insertion code. If no
one else jumps up, I may have time to hit this in the next day or two.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of ahu@casema.net
> Sent: Thursday, December 16, 1999 6:43 PM
> To: openldap-its@OpenLDAP.org
> Subject: Re: Trouble found: substring searches very broken (ITS#402)
>
>
> On Fri, Dec 17, 1999 at 02:36:54AM +0000, ahu@casema.net wrote:
>
> >         for ( ni = 0, ai = 0; ai < ID_BLOCK_NIDS(a); ai++ )
> >         for ( bi = 0; bi < ID_BLOCK_NIDS(b); bi++ )
> >         {
> >                 if ( ID_BLOCK_ID(b, bi) == ID_BLOCK_ID(a, ai) ) {
> >                         ID_BLOCK_ID(n, ni++) = ID_BLOCK_ID(a, ai);
> >                 }
> >         }
> >
> >
> > This however is lots slower and doesn't scale very well
> eventually. It is
> > however the only way to fix the problem on an already indexed
> database. This
> > works instantaneously.
>
> Ok, not quite true, someone could also write idl_sort which would
> take care
> that concatenated blocks do get fetched in the right order.
>
> Regards,
>
> bert hubert.
>
> --
>     +---------------+  |              http://www.rent-a-nerd.nl
>     | nerd for hire |  |
>     +---------------+  |                     - U N I X -
>             |          |          Inspice et cautus eris - D11T'95
>
>