You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/03/21 15:43:14 UTC

[jira] Assigned: (DERBY-876) DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant

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

Knut Anders Hatlen reassigned DERBY-876:
----------------------------------------

    Assign To: Knut Anders Hatlen

> DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
> -------------------------------------------------------
>
>          Key: DERBY-876
>          URL: http://issues.apache.org/jira/browse/DERBY-876
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Reporter: Bernt M. Johnsen
>     Assignee: Knut Anders Hatlen

>
> The result from DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant (is is, however, JDBC 2.0 compliant)
> The returning resultset has one column: TABLE_SCHEM
> From JDBC 3.0, it should have had two columns: TABLE_SCHEM and TABLE_CATALOG
> (See also JDBC 3.0 spec ch. 7.8,)

-- 
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