My argument in favour of MVCC (and why not MULTI_THREADED) to be persistent is
as following:
When restarting H2 Server in a situation where multiple clients are connecting from many different places, it is difficult to set the database to MVCC because
only the first connection can do this and it is very difficult to ensure that your own connection (from a startup script will be the first connection).
I have had this issue in real world in a production environment. What do you
think?
Or could I set MVCC to true using java system properties when starting the server? I quess not since starting the server does not open the database. The
database is opened only when the first connection is made.
- rami
On 05/10/2011 08:30 PM, Thomas Mueller wrote:
Hi,
Most settings could in theory be persistent. But I think it's not
necessary for MVCC and 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.
