RE: searching for >=

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Tony Earnshaw

> tir, 2003-02-11 kl. 21:56 skrev Mike Denka:
>
> > OK.  This nearly answers my last.  I guess the question
> remains whether
> > the consequences of mucking with standard schema are severe.  The
> > compatability issue is pretty obvious.  Any other issues to
> be aware of?
>
> A lot - more and more as time goes on - of core schema attributes are
> now being "built in" to 2.1.x servers, so changing attributes in these
> schemas will utimately have no effect, if you keep your servers up to
> date.
>
> Better to design your own.

In general this is the right answer. In this particular case, I wouldn't be
particularly worried either way. The caveat about core schema above is worth
keeping in mind, but uidNumber is from nis.schema, which comes from the
(expired) RFC2307. It will never migrate into the core. RFC 2307 was only
ever an experimental RFC, which I take to mean "I'm thinking about doing
things like this, use at your own risk, your mileage will vary."
Compatibility and interoperability are nice to maintain, but the spec itself
is ill-defined to begin with, so I would (a) never expect any two
implementations of RFC 2307 to be compatible and (b) have no qualms about
redefining it as needed in my own deployments. On the other hand, since it is
only an experimental schema, the best answer may still be to disregard it and
completely design your own.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support