[ http://issues.apache.org/jira/browse/DERBY-493?page=all ]

A B updated DERBY-493:
----------------------

    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.

  was:
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/CLI.

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


> SQLPROCEDURECOLS will fail with "schema not found" error if it is called when 
> the current schema doesn't exist.
> ---------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-493
>          URL: http://issues.apache.org/jira/browse/DERBY-493
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.1.1.0, 10.2.0.0
>     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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to