Knut Anders Hatlen wrote:
Tim Dudgeon <[email protected]> writes:
Rick Hillegas wrote:
Hi Tim,
If you are running the table function from a jar file stored in your
database, you may have run into the following bug:
http://issues.apache.org/jira/browse/DERBY-4126 This bug is fixed in
the current 10.5 release candidate which we are testing.
Hope this helps,
-Rick
Yes, I am loading jar into DB, so this is almost certianly the problem.
I was not aware of any other way. How else can I access "external" classes?
You can add the jar to the classpath of your application if you're using
embedded Derby. Using ij, you would do something like this:
java -cp /path/to/MyTableFunc.jar:/path/to/derbyrun.jar \
org.apache.derby.tools.ij
Thank you accessing the table function class from the classpath instead
of from a jar loaded into the DB works nicely.
Moving the test class out of the org.apache.derby package tree had no
effect on its own.
Many thanks.
Tim
