Re: Antw: RE: Constraint violation when swapping two unique attributes

[Howard Chu <hyc@symas.com>]

Bannister, Mark wrote:
> Howard Chu wrote:
> > > Ulrich Windl wrote:
> > > > > > > Ulrich Windl schrieb am 20.12.2016 um 08:09 in Nachricht <5858D90F.7AD : 161 : 60728>:
> > > > > > > > "Bannister, Mark" <Mark.Bannister@morganstanley.com> schrieb am
> > > > > > > > 19.12.2016 um
> > > > > 16:43 in Nachricht
> > > > >
> > > > > [...]
> > > > > > Agreed.  LDAP doesn't have a swap operation.  There's a shame.
> > > > > [...]
> > > > >
> > > > > More generally LDAP has no transactions for updates. I wonder if a
> >
> > Wrong, LDAP Transactions are specified in RFC 5805. Please stop posting misinformation to this list.
>
> Interesting.  I see RFC 5805 is classified as "experimental".  How widely is it implemented?  Does OpenLDAP support it?  Does an LDAP client support it?  If they did this would solve my constraint violation problem, I presume.

Support is merged in the OpenLDAP 2.5 release branch.

Unclear that this would help you, which is why I didn't mention it before. It 
depends on when the constraint overlay takes effect. The overlay will still 
see two independent operations, even though a transaction is in place.

You're still better off doing the rename - that will work on all existing LDAP 
implementations.

And to the list in general - you're better off ignoring all of Ulrich Windl's 
posts. He clearly has no idea what he's talking about, and over the past 
couple years has shown no evidence of improving his knowledge.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/