[
https://issues.apache.org/jira/browse/DERBY-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6180:
--------------------------------------
Attachment: DERBY-6180.diff
Attaching a patch which attempts to address this issue by using a method local
to the DatabaseMetaDataTest which loops through all expected column names (and
types and nullability) and checks that there is a matching entries in the
expected column names, types and nullability.
I tested this by modifying arrays of expected items in the test and then
running the test to see if it failed (or passed) as per the changed situation.
> 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
> 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)
