Improve error messages used when Derby can't find the class or method backing
up a SQL routine or type
------------------------------------------------------------------------------------------------------
Key: DERBY-5585
URL: https://issues.apache.org/jira/browse/DERBY-5585
Project: Derby
Issue Type: Improvement
Components: SQL
Affects Versions: 10.9.0.0
Reporter: Rick Hillegas
Priority: Minor
When the code supporting user-written routines and types is put into jar files
in the database, the user also needs to wire the jar files together by setting
the derby.database.classpath property. People often neglect to do this and
Derby documentation in this area could be improved. It would be good to at
least improve the error messages which Derby raises in this situation: 42X50
and 42X51. Those messages should tell the user that one of the reasons for the
failure might be an un/misconfigured derby.database.classpath property. The
following script shows the error messages:
connect
'jdbc:derby:memory:db;create=true;user=test_dbo;password=test_dbopassword';
create function foo( a int ) returns int
language java parameter style java no sql
external name 'Bop.doowop';
create function bar( a int ) returns int
language java parameter style java no sql
external name 'java.lang.Integer.doowop';
values ( foo( 1 ) );
values ( bar( 1 ) );
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
