[ http://issues.apache.org/jira/browse/DERBY-876?page=comments#action_12375557 ]
Dyre Tjeldvoll commented on DERBY-876: -------------------------------------- I have looked at the v1 patch and I think it looks good. I think it can be committed. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
