[Date Prev][Date Next]
Re: (ITS#7226) olcAuditlogFile At dos not accept multiple values
> firstname.lastname@example.org wrote:
>> --On Thursday, April 05, 2012 7:38 PM +0000 email@example.com
>>> On Thu, 5 Apr 2012 13:12:31 GMT, firstname.lastname@example.org wrote:
>>>> email@example.com wrote:
>>>>> firstname.lastname@example.org wrote:
>>>>>> 2. 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
>>> 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
>> I agree. I think defining matching rules where possible is extremely
> Patch welcome. This is a pretty trivial patch to write, but I have more
> 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