Hi Radim
Please make sure you reply in plain text mode, the replies got a bit mixed up.
On Mon, Nov 24, 2014 at 3:07 PM, Radim Vansa wrote:
>
> On 11/24/2014 12:44 PM, Dan Berindei wrote:
>
> Hi Radim
>
>> First of all, I don't think this is feasible. For example, read-committed vs
>> repeatabl
On 11/24/2014 12:44 PM, Dan Berindei wrote:
Hi Radim
First of all, I don't think this is feasible. For example,
read-committed vs repeatable read changes how the entries are stored
in the transaction context, so you can't have a repeatable-read get()
in the same transaction after a read-commi
Hi Radim
First of all, I don't think this is feasible. For example, read-committed
vs repeatable read changes how the entries are stored in the transaction
context, so you can't have a repeatable-read get() in the same transaction
after a read-committed get. Write skew check also requires versions
Hi,
when thinking about strong/eventual consistency and ease of
configuration, I was considering whether cache configuration should
affect results of operations at all (one example could be read
committed/repeatable read, or write skew check).
It would seem to me that the configuration would b
