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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/10/10 22:09:50 UTC

[jira] Commented: (DERBY-2242) Convert jdbcapi/metadata.java to JUnit test.

    [ https://issues.apache.org/jira/browse/DERBY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533858 ] 

Myrna van Lunteren commented on DERBY-2242:
-------------------------------------------

I grabbed this one because I'll be looking at it in reference to DERBY-3088, and it's not seen any action since June.
But - if anyone else wants to try their hand at one of the things left to do...
I assume what's left is what's listed at the top of the test plus 2 TODO's:
 * Methods left to test from JDBC 3
 * 
 *  getBestRowIdentifier
 *  getColumnPrivileges
 *  getCrossReference
 *  getExportedKeys
 *  getImportedKeys
 *  getIndexInfo
 *  getPrimaryKeys
 *  getProcedureColumns
 *  getProcedures
 *  getTablePrivileges
TODO re getSQLKeyworks: //TODO: more testing but not sure what!   
TODO re testUnimplementedSQLObjectAttributes: TODO: types and column names of the ResultSets




> Convert jdbcapi/metadata.java to JUnit test.
> --------------------------------------------
>
>                 Key: DERBY-2242
>                 URL: https://issues.apache.org/jira/browse/DERBY-2242
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Daniel John Debrunner
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>
> Create a test for DatabaseMetaData that matches the testing of metadata.java.
> Should also handle the odbc_metadata variant.
> Once created can be used by other tests to ensure database meta data works in other situations, such as upgrade and read-only databases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.