Hi Thomas, I agree with Rami in the convenience to have a persistent setting for MVCC and MULTI_THREADED, because there are cases where you don't have control over all possible connection sources. Should be an admin user, DBA or design decision what transaction contention scheme to use and possibly other important settings (database properties). This properties should be changed only by admin users for every connection to target database.
Something like: SET MVCC=true; If URL don't specify MVCC, then remain true for every connection until SET to false in the same way. If URL specify MVCC to a value distinct than persisted value for an existing database , then a connection error must be throw. If URL specify MVCC value equal to persisted value for an existing database, then connection ok. If URL specify MVCC value for a NON existing database, then database is created with specified values persisted and connection ok. regards, Dario. El 18/05/11 00:58, Thomas Mueller escribió: >> only the first connection can do this > I suggest to add the setting on _all_ database URLs, not just the > first one. It's not correct that only the first connection may contain > those settings: all connections to a database may contain them. Just > make sure that all database URLs are the same (well, you anyway need > to ensure that) -- 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.
