On 2/11/2011 1:41 PM, Thomas Mueller wrote:
Hi,
Yes, this is a bug, it will be fixed in the next release. If you want,
you can already test it in the trunk:
http://code.google.com/p/h2database/source/checkout
Nice.
any news in adding "jdbc:default:connection"
Yes, I will add support for this feature in the next release, however
it will be disabled by default. You will need to append
;DEFAULT_CONNECTION=true to the database URL. This feature is disabled
by default for performance reasons. Please note the Oracle JDBC driver
will try to resolve this database URL if it is loaded before the H2
driver (there is nothing H2 can do about that).
Great! I had implemented it myself to see if i could but never submitted
a patch because I have no idea how to make one of those diff files. :) I
added a threadlocal to the driver with the connection and I registered
the connection with the driver before each procedure call in
FunctionAlias and unregistered it after the call returned. Surprisingly
simple and worked fairly well.
AFAIK all drivers probably suffer from the same problem (resolve
"jdbc:default:connection").
From what I understand "jdbc:default:connection" is only used in stored
procedures/triggers/etc which means it runs in the server so i *think*
there is no reason for conflict. I guess maybe in some weird replication
where the database server loads jdbc drivers.
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.
