|Subject||Re: how to swap two values on a uniquely constrained column?|
--- In firstname.lastname@example.org, Dimitry Sibiryakov <sd@...> wrote:
>It's serious as any consistency problem on any state domain. In this particular case, two rows with the same ORDER_INDEX value would prevent re-ordering from working on the client app.
> > Obviously to preserve the custom ordering. Two rows of same ORDER_INDEX don't have a definite order.
> But how they can get the same value if you handle ORDER_INDEX properly?
> I mean that unique constraints are supposed to prevent serious data
> problems. Custom ordering isn't critical enough.
> SY, SD.