[
https://issues.apache.org/jira/browse/DERBY-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148081#comment-14148081
]
ASF subversion and git services commented on DERBY-6180:
--------------------------------------------------------
Commit 1627578 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1627578 ]
DERBY-6180; DatabaseMetaDataTest should not fail if there are extra columns but
only check the expected ones
Moving the assertDatabaseMetaDataColumns method to junit.JDBC and making
jdbc4.TestDbMetaData use 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
> 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)
