Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5585

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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 10.9.1.0
    • 10.13.1.0
    • SQL
    • Normal
    • Known fix, Newcomer

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

      Attachments

        1. Derby-5585_2.diff
          3 kB
          Danoja Dias
        2. Derby5585_3.diff
          4 kB
          Danoja Dias
        3. Derby-5585.diff
          2 kB
          Danoja Dias
        4. errors.zip
          2 kB
          Bryan Pendleton

        Issue Links

          Activity

            People

              Dnj Danoja Dias
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: