[DERBY-493] SQLPROCEDURECOLS will fail with "schema not found" error if it is called when the current schema doesn't exist.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 10.1.1.0, 10.2.1.6
• Component/s: JDBC
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: High Value Fix
• Assignee: Unassigned
• Reporter: A B
• Created: 05/Aug/05 05:28
• Updated: 03/Sep/14 08:31
• Resolved: 28/Dec/12 19:13

Description

The SQLPROCEDURECOLS procedure that Derby defines internally to handle the DatabaseMetaData.getProcedureColumns() call (in JDBC) and the SQLProcedureColumns() call (in ODBC) will fail with "schema not found" error if it is called when "current schema" doesn't exist. This is a problem with Derby embedded, and thus can be seen from embedded mode, server mode (JDBC), and ODBC.

None of the other metadata procedures have this problem; only SQLPROCEDURECOLS.