Re: attributes with empty values

[Jeff Warnica <jeffw@chebucto.ns.ca>]

I cant say if its a LDAP restriction, a OpenLDAP restriction, or an
error on your part that pervents empty values.. I suspect its an LDAP
restriction / design... Most attrs can be multivalued, or not there at
all; apps using LDAP data shold be aware of this and capable of dealing
with mutiple, or non existant, values.

Clearly, if a atttribute is required by the schema, then its required by
something more then just the schema definitions: its there for a reason.
Having a (required) attr with a null value would almost definitly cause
pain for whatever required that atttr to be a requirement.

On Sun, 2003-12-07 at 12:38, Ace Suares wrote:

> Is this a problem with the SYNTAX of the attribute, or is this a general 
> thing?
> Ans is the only way to effect an 'empty' valued attribute, to remove the 
> attribute fromt he entry ? I believe it works that way, but I'd like 
> confirmation. I think I can understand why values may not be 'empty' but 
> can't there be situations where an attribute is a MUST in the schema but can 
> have the empty string as one of it's possible values ?