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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/10/21 20:53:44 UTC

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

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

Kathey Marsden updated DERBY-876:
---------------------------------

    Fix Version/s:     (was: 10.2.1.6)
                   10.1.3.2

> DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
> -------------------------------------------------------
>
>                 Key: DERBY-876
>                 URL: https://issues.apache.org/jira/browse/DERBY-876
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: Bernt M. Johnsen
>            Assignee: Knut Anders Hatlen
>             Fix For: 10.1.3.2
>
>         Attachments: derby-876-v1.diff, derby-876-v1.stat
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.