Hi, On Thu, Apr 4, 2013 at 8:31 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > On Thu, Apr 4, 2013 at 8:08 PM, Alex Parvulescu > <alex.parvule...@gmail.com> wrote: >> right, it would appear that OAK-748 introduced this problem, but it's not >> that easy to take it all out. > > Yep, that looks like the case.
The problem was the uniqueness check that ended up being done separately for each individual property change instead of once per commit. The result was that something like moving a referenceable node from /a to /b would show up as a uniqueness breach if the addition of /b got processed before the removal of /a. I fixed the issue in revision 1464823. BR, Jukka Zitting
