[
https://issues.apache.org/jira/browse/DERBY-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-493:
---------------------------------
Urgency: Normal
Triaged July 10, 2009: assigned normal urgency.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
