db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-876) DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
Date Tue, 21 Oct 2008 16:27:46 GMT

    [ https://issues.apache.org/jira/browse/DERBY-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641425#action_12641425
] 

Kathey Marsden commented on DERBY-876:
--------------------------------------

I received a request to backport this fix to 10.1.  I think I will just change the getSchemas
query in metadata.properties as the new getSchemas call does not exist there.  There will
still be the problem of DERBY-1107 for existing databases, but it should correct the problem
for new databases.


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


Mime
View raw message