https://bugs.openldap.org/show_bug.cgi?id=9295
--- Comment #10 from Ondřej Kuzník <[email protected]> --- On Fri, May 28, 2021 at 10:20:59PM +0000, [email protected] wrote: >> The way we munge the inbound op can backfire on operations like this: >> >> ``` >> add: singlevalued >> singlevalued: new >> - >> delete: singlevalued >> singlevalued: old >> ``` >> >> Arguably, applications that do this are strange, but the protocol allows >> this and it's accepted on the provider. > > Note that it's not strange at all: This is the recommended client behaviour > when using an ID pool entry for unique ID assignment. I'm not sure what the difference is to just sending a delete, then add from application's point of view? I know it shouldn't matter as the entry only needs to be consistent/valid when the operation is finished, but you're saying there are reasons to do just this... -- You are receiving this mail because: You are on the CC list for the issue.
