No, we didn't. But the current behavior is broken, so if people are expecting our skiplists to act like "real" skiplists, it will fail. I think fixing broken should be allowed...
> On Mar 5, 2015, at 11:29 AM, Ruediger Pluem <[email protected]> wrote: > > > > On 03/05/2015 05:19 PM, Jim Jagielski wrote: >> After doing some additional research, I think that the >> current implementation of NOT allowing duplicates (in >> APR 1.5/1.6) is BROKEN. In trunk this is determined by >> a flag w/ the insert statement, but the default *should* >> be to allow dups. >> >> As such, I'd like to adjust 1.5/1.6 to the correct and, >> afaict, canonical behavior. >> >> > > Guess this is fine for 1.6 as it is not released yet. I am not so sure for > 1.5 as it has been released and this is a > change in behavior. Did we made any promises on the current behavior in 1.5? > > Regards > > Rüdiger
