Derby
  1. Derby
  2. DERBY-493

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

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 10.1.1.0, 10.2.1.6
    • Fix Version/s: None
    • Component/s: JDBC
    • Urgency:
      Normal
    • Issue & fix info:
      High Value Fix

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            A B
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development