Re: Constraint Violations

[Steven Legg <s.legg@trl.telstra.com.au>]

Eric,

Erik Skovgaard wrote:
> 
> Jim,
> 
> I agree with your interpretation of the standards, however, I have seen a
> product that returned a constraint violation when I tried to break the syntax.
> 
> BTW, some products do not check for Upper Bounds at all.

Which is perfectly legal in X.500. Annex C of X.520, where the upper bounds
are given, is not an integral part of the standard. The values are only
suggestions and an implementation is free to use different bounds or no
bounds at all.

Regards,
Steven

> 
> Cheers,                    ....Erik.
> 
> ------------------------------------
> Erik Skovgaard
> GeoTrain Corp.
> Enterprise Directory Planning
> http://www.geotrain.com
> 
> At 12:06 99/06/21 -0600, Jim Sermersheim wrote:
> >When an attribute uses the wrong syntax (or a malformed syntax) I would
> >expect to see the invalidAttributeSyntax error.  I think
> >constraintViolation is typically used for size and value boundary
> >conditions.  There are probably grey areas like C=USA, should that be a
> >constraint violation or an invalid syntax?
> >
> >>>> Erik Skovgaard <eskovgaard@geotrain.com> 6/21/99 11:27:36 AM >>>
> >Shiv,
> >
> >A constraint violation would typically happen if you try and add an
> >attribute that either uses the wrong syntax or where the maximum length
> >has
> >been exceeded.  A very typical example is the postalAddress attribute
> >which
> >is constrained to a maximum of six lines of 30 characters.  Many of
> >the
> >database loads I have done seem to stumble here because one or more of
> >the
> >address components are longer.
> >
> >I do not have an exhaustive list of situations that may cause problems,
> >but
> >perhaps this will point you in the right direction.
> >
> >Cheers,                  ....Erik.
> >
> >------------------------------------
> >Erik Skovgaard
> >GeoTrain Corp.
> >Enterprise Directory Engineering
> >http://www.geotrain.com 
> >
> >At 11:27 99/06/21 +0530, Shiv Shankar Ramakrishnan wrote:
> >>Hi,
> >>
> >>1. What is the exhaustive list of conditions under which a constraint
> >>   violation error occurs? 
> >>
> >>   I checked with the Netscape C SDK documentation and it doesn't
> >seem
> >>   to give very exhaustive information. The draft C api text also
> >>   doesn't seem to give much info about this. RFC 2251 refers to an
> >>   AttributeProblem but doesn't elaborate on it.
> >>
> >>2. What is the semantic meaning of a constraint violation error? I am
> >>   not very clear from the what info I could find on it.
> >>
> >>3. Is the constraint violation signalled for Syntax violations? E.g.
> >If
> >>   an attribute has an Integer syntax and some non digit chars are
> >sent.
> >>
> >>   What errors are signalled for attribute syntax violations?
> >>
> >>   I think none are since in RFC 2251 section 4.1.6 says that -
> >>   "Clients MUST NOT send attribute values in a request which are not
> >>   valid according to the syntax defined for the attributes."
> >>   Then what is the value of specifying a syntax if all the checking
> >>   is done by the client? Shouldn't the directory return an error?
> >>   Isn't LDAP being too lightweight here :-)
> >>
> >>4. Where else can I find more info about errors in LDAP as defined by
> >>   the v3 spec?
> >>
> >>Thanks in advance,
> >>Shiv
> >>
> >>
> >>
> >
> >
> 
>