On Mon, Apr 07, 2014 at 09:21:29AM +0000, Bernhard Reiter wrote:
> 
> Shouldn't REPEATABLE READ be the default then?

This depends on what your goal is. For me it's worse that users get a
serialization error (in our current web interface the users sees "An
error has occurred") and possibly lose their submitted data than the
occasional wrong history entry. But this depends on your application and
what the history is used for.

'read commited' could also have other inconsistencies (e.g., if an
auditor computes values over a table and stores the result in the
database). But I think we don't have any applications with that
behaviour in the default tracker schemas shipped.

Note that setting this higher for mysql is probably less problematic
because mysql seems to use locking and the two transactions would both
go through, one after the other. I've not tested this, though.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com
allmenda.com member                     email: rsc@allmenda.com