Hi, > 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. :)
With Eclipse, use Team / Create Patch, with Linux, you can use the "diff" command line tool. > 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. That's what I did as well. See http://code.google.com/p/h2database/source/detail?r=3359 http://code.google.com/p/h2database/source/diff?spec=svn3359&r=3359&format=side&path=/trunk/h2/src/main/org/h2/engine/FunctionAlias.java > AFAIK all drivers probably suffer from the same problem (resolve > "jdbc:default:connection"). No. It's (in my view) a bug in the Oracle driver. If the Oracle JDBC driver doesn't have jdbc:default:connection connection, it should simply ignore the call. However, it doesn't. The Oracle driver thinks it's the only driver in the system that is "allowed" to support 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. If there are multiple JDBC drivers installed on the server then it *is* a problem. 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.
