improve locking behavior for transaction

Description

Due to changes in the SailConnection API, the current implementation of locking in native and possible memory store blocks concurrent reads as soon as SailConnection.begin() has been called. Read blocking should be delayed until first actual write operation has commenced.

See http://sourceforge.net/mailarchive/message.php?msg_id=30425287

Environment

None

Status

Assignee

Jeen Broekstra

Reporter

Jeen Broekstra

Labels

None

Components

Fix versions

Affects versions

Priority

Critical
Configure