Hi,

The cluster mode is also an area that is not very well tested. And using
LOCK_MODE=0 is not recommended (even when not using a cluster).

What problem do you want to solve? Why don't you just use the default
settings?

Regards,
Thomas


On Sun, Jan 13, 2013 at 3:32 PM, Ryan How <[email protected]> wrote:

>  I'm not sure sorry, someone else might be able to answer for you. I
> could only suggest give it a go and see if it works. I don't see why it
> wouldn't work, you are only changing transaction isolation level.
>
> Thanks, Ryan
>
>
> On 13/01/2013 6:24 PM, Matouš Voldřich wrote:
>
> Thanks for answer. We will give it a try and at write some tests.
>
>  Could you answer my second question? Is it possible to set LOCK_MODE=0
> and still use cluster mode?
>
>  Thanks
> Matous
>
> Dne sobota, 12. ledna 2013 15:34:27 UTC+1 Kartweel napsal(a):
>>
>>  MVCC has been around for a while, so it is pretty stable. But I did
>> find a bug the other day with "for update" and lobs, so it still has bugs.
>> It isn't as well tested as the rest of the engine, and not as well
>> supported :)
>>
>> Ryan
>>
>> On 11/01/2013 6:35 PM, Matouš Voldřich wrote:
>>
>> Hi,
>>
>>  I would like to ask about H2 feature MVCC (multi version concurrency).
>> On some places this feature is marked as experimental so I would like to
>> ask about its status. Is it ussable?
>>
>>  We would like to prevent locking of entire table. Are there any other
>> options? I found only to use LOCK_LEVEL=0 since we do not need transactions
>> at all (we use it as simple INSERT-GET-UPDATE-DELETE store). But we also
>> use cluster, so I'm not sure if setting it will not disable the cluster
>> functionality as well.
>>
>>  Thanks.
>> Matous
>> --
>> You received this message because you are subscribed to the Google Groups
>> "H2 Database" group.
>> To view this discussion on the web visit https://groups.google.com/d/**
>> msg/h2-database/-/IPVunNjiwuUJ<https://groups.google.com/d/msg/h2-database/-/IPVunNjiwuUJ>
>> **.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to h2-database...@**
>> googlegroups.com.
>> For more options, visit this group at http://groups.google.com/**
>> group/h2-database?hl=en<http://groups.google.com/group/h2-database?hl=en>
>> .
>>
>>
>>   --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/h2-database/-/vImI06FfFZMJ.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to