Hello,
I have some troubles in the creation of a ldap schema.
I would like something like that:
attributetype ( eloOrganizationalUnitAttribute:7.30.2008.1.22 NAME 'street' DESC 'Cinema street' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch ORDERING caseIgnoreOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} SINGLE-VALUE ) attributetype ( eloOrganizationalUnitAttribute:7.30.2008.1.23 NAME 'postalCode' DESC 'Cinema Zip code' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch ORDERING caseIgnoreOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} SINGLE-VALUE )
When I restart slapd, I have an error (but no output was produced) ans there is nothing niteresting in syslog.
If I change the attributes' names (street -> cstreet, postalCode -> cpostalCode for instance), all works fine.
I could keep my schema like that but it's not very beautiful.
Do you know what's happen ? I have seen some schema over the net which use 'street' and 'postalCode' and without problems. I'm a bit jalous :)
Thank you !
nicolas@gibelin.fr wrote:
attributetype ( eloOrganizationalUnitAttribute:7.30.2008.1.22 NAME 'street'
attributetype ( eloOrganizationalUnitAttribute:7.30.2008.1.23 NAME 'postalCode'
You're reusing NAMEs of other attribute types with different OID.
When I restart slapd, I have an error (but no output was produced) ans there is nothing niteresting in syslog.
Start "slapd -d 65535".
If I change the attributes' names (street -> cstreet, postalCode -> cpostalCode for instance), all works fine.
Yupp. As expected since 'street' and 'postalCode' are already defined in core.schema and you leave it that way.
I could keep my schema like that but it's not very beautiful.
What exactly do you want to achieve? If you have your own object class you can simply use 'street' and 'postalCode' therein without redefining these attribute types.
Ciao, Michael.
Indeed, you're right, I didn't see that I could use predefined attributes.
I've changed them and all works fine, thank you !
Nicolas
openldap-technical@openldap.org