qazmlp a écrit :
I'm sorry, still I do not get it.
How can you predict the min, max values to inject them as part of the LDAP
search filter?
Damn ! Either I'm an idiot, or I need two more coffees :(
I though you had a place where you stored those lower/higer ranges, to
be able to use them in your filter...
The problem is that you can't do such things like (&(productId >=
lowerRange) ...) in ldap.
A control won't help, unless you are able to implement it directly in
the server. An extendedRequest might be easier, but you still have to
implement it.
What about using a multivalued attribute in your entries, containing all
the possible values in the range :
entry-1 :
product-id: 15-22
ids: 15
ids: 16
ids: 17
ids: 18
ids: 19
ids: 20
ids: 21
ids: 22
<other attributes>
Ok, this is really a brute force approach, but at least, the duplication
is limited.
On the other side, if I understand what you are trying to do, ie
limitating duplication of common attributes between products, I would
suggest that your products directly link to these common attributes :
productId: 18
commonAttrs: products15-22
<specific product attributes>
productRange: products15-22
colour: white
size: small
<other common attributes>
Doing so while force you to do 2 requests to the server : one to get the
range, one to get the attributes.
wdyt ?
Emmanuel
---
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.
---
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.
