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] Commented: (DERBY-876) DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
Date Tue, 21 Mar 2006 15:01:24 GMT
    [ http://issues.apache.org/jira/browse/DERBY-876?page=comments#action_12371242 ] 

Knut Anders Hatlen commented on DERBY-876:

JDBC 4.0 has a getSchema(String, String) which was implemented in
DERBY-968. That method does return the two columns.

If we modified EmbedDatabaseMetaData.getSchemas() to just call
getSchemas(null, null) we would get the correct behaviour. This way,
we don't have to modify metadata.properties, so there should not be
any SPS upgrade issues.

Output from the metadata test will however change (extra column with

> 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:
For more information on JIRA, see:

View raw message