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 2014/09/25 20:24:34 UTC

[jira] [Resolved] (DERBY-6180) DatabaseMetaDataTest should not fail if there are extra columns but only check the expected ones

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

Myrna van Lunteren resolved DERBY-6180.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.12.0.0

As this is marked an improvement in test, I don't intend to backport it.

> DatabaseMetaDataTest should not fail if there are extra columns but only check the expected ones
> ------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6180
>                 URL: https://issues.apache.org/jira/browse/DERBY-6180
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Kathey Marsden
>            Assignee: Myrna van Lunteren
>             Fix For: 10.12.0.0
>
>         Attachments: DERBY-6180.diff, DERBY-6180_2.diff
>
>
> In new JDBC versions colums can be added  to DatabaseMetaData. Tests should just check expectedColumns and ignore extra columns to prevent failures with compatibility testing.
> This check occurs in assertColumnNames and assertColumnTypes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)