Hmmm, this integerBitOrMatch and integerBitAndMatch patch is intriguing to me, is there any technical reason this is only on HEAD?
Could I patch it into 2.0.21 and just start to use it?
(assuming of course that I were to make my own schema attributes that took advantage of it?)
-----Original Message-----
From: Norbert Klasen [mailto:norbert.klasen@daasi.de]
Sent: Thursday, January 31, 2002 4:10 AM
To: Upma Gandhi; openldap-software@OpenLDAP.org
Subject: Re: Do we have Wild card like "."
--On Donnerstag, 31. Januar 2002 13:30 -0500 Upma Gandhi
<upma@npi.stpn.soft.net> wrote:
> To address this thing, what I'm doing is , I'm taking this DOM as 4
> bytes string ( 31 days= max of 4 bytes, where each bit represnt that
> particular day).
> so, to store this 4-7 days range, I'm setting bit number 4 to 7 to
> "1", rest all bit position to "0".
> so, 4-7 range can be stored in LDAP schema as a concatenation of
> (31-7) zeros followed by 1111000 or more pictorically -
>
> |__________|__________|__________ |__________ |
> | 0 0 0 00000| 0 0 00000 0 | 00000000 | 01 1 1 1 0 00|
> |--------|--------|--------|--------|
>
> Suppse , today is 5'th day of month and I want to see
> whether this DOM field of any record (suppose this DOM is part of one
> record) is set or not
You might be able to make DOM a bitString and use the matching rules from
http://www.openldap.org/lists/openldap-bugs/200109/msg00000.html
--
Norbert Klasen
DAASI International GmbH phone: +49 7071 29 70336
Wilhelmstr. 106 fax: +49 7071 29 5114
72074 Tübingen email: norbert.klasen@daasi.de
Germany web: http://www.daasi.de