Hi, > I thought the H2 docs had said > that connection pooling was actually slower than just creating new > connections. > But, now the docs say that the new built-in connection > pool is 50% faster. So, am I correct in saying that the new built-in > connection is now the recommended way to handle connections, even in > embedded mode?
I just found out (today) there are some bugs in the built-in connection pool (actually in the JdbcDataSource that is used by the connection pool). I will fix them, hopefully in the next release everything works as expected. > I'm using H2 in embedded mode with Hibernate and I'm wondering what is > the best way to handle connections. Currently, the best way is to use DriverManager.getConnection(...). In most cases it doesn't matter: unless you open and close a lot of connections per second you will not see a difference. 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 -~----------~----~----~----~------~----~------~--~---
