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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on DERBY-6180:
--------------------------------------------------------

Commit 1627436 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1627436 ]

DERBY-6180; DatabaseMetaDataTest should not fail if there are extra columns but only check the expected ones
   Making DatabaseMetaDataTest use a local method that only checks the expected columns.

> 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
>         Attachments: DERBY-6180.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)