db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2242) Convert jdbcapi/metadata.java to JUnit test.
Date Fri, 23 Nov 2007 22:38:43 GMT

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

Myrna van Lunteren resolved DERBY-2242.

       Resolution: Fixed
    Fix Version/s:

I converted the remaining test cases that needed  it  with revision 597311, and removed the
old  files with revision 597464.

For intermediate changes, please see the svn revision log...

One note: metadata_test.java had a section marked 'beetle 4620'. It refered to edge case testing
the algorithm for getColumns in metadata.properties that sets max integer for octet_length
when the datatype is char or varchar with length > max integer / 2 ....
However, I think since then, there's been a change in the max size of the char/varchar, to
size 32672, and the test case was adjusted accordingly.
I am wondering if that code in metadata.properties is still necessary...

> 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
>             Fix For:
> 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.

View raw message