[DERBY-5585] Improve error messages used when Derby can't find the class or method backing up a SQL routine or type

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.13.1.0
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Known fix, Newcomer
• Assignee: Danoja Dias
• Reporter: Richard N. Hillegas
• Created: 24/Jan/12 17:22
• Updated: 01/Aug/16 06:23
• Resolved: 30/Jul/16 01:54

Description

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 ) );

Issue Links

• is depended upon by: DERBY-6870 Google Summer of Code 2016: Derby bug fixing