[rucksack-devel] Transactions: abort early?

[Nikodemus Siivola]

"Arthur Lemmens" <alemmens at xs4all.nl> writes:

> I don't think there's a problem here.  T1 is now free to change O and/or
> commit, and there still won't be a problem.
>
> But maybe I'm missing something?

I don't think so -- I see where my think'o was.

 I was assuming there were some (invisible to the transaction system)
constraints between O and the rest of the world, that would be
violated if T1 saw the changed O -- which is nonsense. (Eg: every time
you touch O increment C.)

If the constraints have been violated, there is nothing the
transaction system can do about it. If they have not been violated,
then everything is fine. (And if both C and O are prevalent then
the conflict is real, of course.)

Cheers,

  -- Nikodemus              Schemer: "Buddha is small, clean, and serious."
                   Lispnik: "Buddha is big, has hairy armpits, and laughs."