[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Substrings in attributes - changing schemas

Any suggestions, anyone?

Let me rephrase the questions (hoping to help in replying):

  1. In (very) short: Is there any way we can search substrings of
     values in attributes not having a SUBSTR matching rule defined,
     without modifying the schema(s)?
  2. If I expand the definition of an attribute - by adding a SUBSTR
     matching rule - in a widely distributed schema in cosine.schema,
     is there any serious risk which I should consider?


On 8/1/2011 5:12 μμ, Nick Milas wrote:

I store my DNS records in openldap (I use powerdns with ldap backend) and I am trying to use a search filter like: (aRecord=10.11.12.*) but it never produces results.
I came to the conclusion that the problem may be caused by the fact that aRecord (oid: 0.9.2342.19200300.100.1.26) in cosine.schema has no substring matching rule defined in schema:

   attributetype ( 0.9.2342.19200300.100.1.26 NAME 'aRecord'
            EQUALITY caseIgnoreIA5Match
            SYNTAX )

I thought of modifying it in order to allow substring matching, like:

   attributetype ( 0.9.2342.19200300.100.1.26 NAME 'aRecord'
            EQUALITY caseIgnoreIA5Match
            SUBSTR caseIgnoreIA5SubstringsMatch
            SYNTAX )