Excerpts from Adam Chlipala's message of Tue Nov 30 00:37:53 +0100 2010:
Couldn't you just as easily write a C function that takes options as
input and then always executes verify-pay-confirm with those options?
That would make sure the Ur/Web layer can't introduce zany
non-transactional
Marc Weber wrote:
Excerpts from Adam Chlipala's message of Sun Nov 28 21:58:18 +0100 2010:
That's right. The runtime system will also restart if an optimistic SQL
concurrency violation is detected, when certain errors are signaled, etc..
Don't know yet whether that's smart
Excerpts from Adam Chlipala's message of Sun Nov 28 21:58:18 +0100 2010:
That's right. The runtime system will also restart if an optimistic SQL
concurrency violation is detected, when certain errors are signaled, etc..
Don't know yet whether that's smart behaviour.
How exactly is determined
