I don't really understand what you are saying.
All statements (whether they be selects, updates, deletes or inserts)
are always within transactions.
So what is the difference between a long running transaction and long
running query?
Maybe long running query could be interpreted as long running
transaction that has only selects in it.
So if this is the case then what you say is that if I have a transaction
that has many updates I should be getting
better concurrency with mvcc.
But at the moment my tests indicate that a long running updating
transaction seems to block all other activity (= queries) completely.
Do you think that I have just make a mistake somewhere or could this be
possible?
- rami
On 16.6.2010 20:26, Thomas Mueller wrote:
It has already been said, so just to repeat: if you have long running
transactions, MVCC is better. If you have long running queries,
MULTI_THREDED is better. If you both at the same time, then it's a
problem, because both features combined is not supported yet. See
also:
http://h2database.com/html/advanced.html#mvcc
http://h2database.com/html/grammar.html#set_multi_threaded
Regards,
Thomas
--
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.
