>dn:productID=15+productID=16+productID=17+productID=18+productID=19+productID=>20+productID=21+productID=22, <remainingPartsOfDN> >colour: White >size: small ><other attribute values> To make it optimal, I can also mention only the min and max values in the RDN part and then include all the values in a range as part of the attribute-value definition. E.g. dn:productID=15+productID=22,<remainingPartsOfDN> productID:15 productID:16 .... productID:22 colour: White size: small <other attribute values>
This approach also helps in directly finding out the min and max values of the range where the given attribute belongs to. > >my requirement can be easily fulfilled with the multi-valued RDN > >attribute. > > > Sure, but I warn you that it will be heavy and not really performant. Is that really the case? My understanding is that if we keep the values as part of the RDN(and not as a non-RDN-multi-valued as shown in your approach) attribute, then the search will be faster. In general, the search for a key/RDN is expected to be faster than the search for a non-key/non-RDN attribute, for LDAP/oracle. Isn't it? --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
