Hi, El 03/12/10 20:56, kimyx escribió: > UDFs are working well for us but I like the fact that > the link table has indexes defined when doing joins within h2.
If your UDF return an ResultSet (or constructed SimpleResultSet class), that can be used as a table too for anything you want. > We have the following in our jboss datasource, which normally takes > care of providing a new connection when the socket is broken: > > <exception-sorter-class- > name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</ > exception-sorter-class-name> > <valid-connection-checker-class- > name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</ > valid-connection-checker-class-name> > > I think h2 circumvents this by keeping a particular connection object > around for the life of the server. I tried setting > h2.shareLinkedConnections to false but it didn't help with this issue. Interesting approach, but that create a new connection that don't replace wrapped connection in linked table. Linked tables start unconnected until the first access and remain connected for session's life. So, what's lacking here is something that can detect connection lost,reconnect and renew waped connection , on internal methods of linked tables that make use of external conn. . > I'll try fiddling with some mysql parameters. Otherwise, I have the h2 > source checked out and compiling, so maybe I'll try patching it Would be an useful an elegant extension of this feature. Regards, Dario -- 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.
