--=-s2sha8beM9nUssvA07HS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable
On Tue, 2008-05-27 at 18:43 -0700, Howard Chu wrote:
Andrew Bartlett wrote:
On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote:
=20
This needs to occur even between databases on the server, but I won't=
ask that
it occur outside the known trees.
It's already possible for operations in one database to reference entr=
ies in a
different database, so that aspect of validation should be fine. Howev=
er, as
noted before, "validation" is generally bogus to begin with. In partic=
ular,
how do you create entries with circular references? If you disallow re=
ferences
to nonexistent entries, you can't set the references until after all o=
f the
entries have been created. This means that you cannot backup a databas=
e that
has these references and then later reload it in a single pass.
An interesting point, but I need to match the windows runtime behaviour.
=20 Only when it has a visible impact on other clients. What software will br=
eak=20
if the directory allows you to add new entries that contain dangling=20 references? What will break if the directory allows you to modify a refer=
ence=20
attribute to point to a nonexistent entry?
Sure, I'm not asking for a change to default behaviours. I'm listing the things that our testsuite finds are differences, and looking for solutions.=20
There's a lot of Windows behavior that is clearly wrong, by any number of=
=20
metrics. You need to be a bit more selective in prioritizing the list of=20 things to chase down.
This is the currently the top priority for an LDAP Backend for Samba4. =20
Andrew Bartlett
--=20 Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc.
--=-s2sha8beM9nUssvA07HS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part
--=-s2sha8beM9nUssvA07HS--