Emmanuel, please stay on the list with replies. Thanks.
Yes, 'integerOrderingMatch' (instead of 'integerMatch' as I wrongly stated) is needed for the filter mentioned before. Similar 'numericStringOrderingMatch' for 'NumericString' syntax. Thanks for pointing that out. Ciao, Michael. Emmanuel Lecharny wrote: > > there is just one thing to check : is your server support the > integerOrderingMatch matchingRule (I wasn't aware of such a > matchingRule, which is defined in the very helpful RFC 3698). OpenLdap > support it since version 2.1 I suppose, but in 2.3 for sure. > > Thanks Michael for this information :) > > Michael Ströder a écrit : > >> Emmanuel Lecharny wrote: >> >> >>> This sounds a good idea, but be aware that again, this is a String >>> comparizon, not a numeric one. >>> >>> Something like : >>> (&(00067>minRangeBoundary)(00067<=maxRangeBoundary)) >>> >>> would work, I think (assuming that you store IDs between 0 and 999 999) >>> >> >> This depends on the LDAP syntax and matching rules used for >> minRangeBoundary and maxRangeBoundary. One has to decide whether to use >> syntax >> >> 'Integer' (OID 1.3.6.1.4.1.1466.115.121.1.27) with matching rule >> 'integerMatch' (OID 1.3.6.1.4.1.1466.115.121.1.27) or >> >> 'Numericstring' (OID 1.3.6.1.4.1.1466.115.121.1.36) with matching rule >> 'numericStringMatch' (2.5.13.8). >> >> Ciao, Michael. --- You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
