db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-876) DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
Date Fri, 21 Apr 2006 12:25:07 GMT
     [ http://issues.apache.org/jira/browse/DERBY-876?page=all ]

Knut Anders Hatlen updated DERBY-876:

    Attachment: derby-876-v1.diff

Attaching a patch which adds the TABLE_CATALOG column to the result
set returned by EmbedDatabaseMetaData.getSchemas(). The client does
the right thing automagically after this change.

Canons for metadata, odbc_metadata, and Upgrade_10_1_10_2 had to be

Derbyall (including JCC tests) and the upgrade test ran successfully
on Sun JVM 1.5. Metadata test ran successfully on JVM 1.3 and 1.5 on
embedded, DerbyNetClient and DerbyNet. The jdbc40 suite also ran

Please review the patch! Thanks!

> 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
>  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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message