quanah@zimbra.com wrote:
--On Thursday, April 05, 2012 7:38 PM +0000 h.b.furuseth@usit.uio.no wrote:
On Thu, 5 Apr 2012 13:12:31 GMT, michael@stroeder.com wrote:
hyc@symas.com wrote:
michael@stroeder.com wrote:
- add an equality matching rule.
My approach with config attrs has been to skip the equality rule for single-valued attrs. Since they are single-valued, there's obviously no need to allow for comparing multiple values.
Users always find more ways to use a feature than its creator imagined.
I wish people would give attributes all matching rules they can. Equality, ordering, substring. Except when:
- flexibility would be a misfeature, e.g. SUBSTR for userPassword,
- or it's unclear which rules to choose, e.g. caseIgnore vs
caseExact.
I agree. I think defining matching rules where possible is extremely useful.
Patch welcome. This is a pretty trivial patch to write, but I have more urgent things to attend to.
In general, I also prefer to have NO matching rules associated to attrs designed for purposes that do not require matching (this is often the case of configuration-specific attributes mostly if not only intended for internal use). Whenever one needs to search them, extensible filtering is your friend.
p.