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

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen resolved DERBY-493.
--------------------------------------

    Resolution: Cannot Reproduce

I tried to reproduce this problem by executing the following code snippet:

        Connection c = DriverManager.getConnection("jdbc:derby:db;user=nosuchschema;create=true");
        ResultSet rs = c.getMetaData().getProcedureColumns(null, "%", "%", "%");
        while (rs.next());
        rs.close();

It fails with "ERROR 42Y07: Schema 'NOSUCHSCHEMA' does not exist" on Derby 10.1 (tested with 10.1.1.0, 10.1.2.1 and 10.1.3.1). However it does not reproduce on 10.2.1.6 and higher, so I'm assuming the problem that's described here has been fixed.

Resolving the issue.
                
> SQLPROCEDURECOLS will fail with "schema not found" error if it is called when the current schema doesn't exist.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-493
>                 URL: https://issues.apache.org/jira/browse/DERBY-493
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.1.1.0, 10.2.1.6
>            Reporter: A B
>              Labels: derby_triage10_5_2
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira