[
https://issues.apache.org/jira/browse/DERBY-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275261#comment-15275261
]
Bryan Pendleton commented on DERBY-3181:
----------------------------------------
Indeed, it looks like I am still seeing some problems in the upgradeTests, too.
But my results are not the same as yours. Can you look in your results?
You should have a directory named "junit_YYYYMMDD_HHMM" in your trunk
directory, and in there should be all the results of your testing. There
should be a file named
TEST-org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite.xml
and that file should have information about each test failure. In that
file, use your text editor to search for the strings 'error message=' and
'failure message=' to see information about each error and each test failure.
In my case, my results were:
[junit] Tests run: 6439, Failures: 14, Errors: 0, Skipped: 0, Time elapsed:
2,491.535 sec
[junit] Test
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite FAILED
and in my XML file I see only one failure, but the same failure occurred
all 14 times:
<testcase
classname="org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest"
name="testGetTypeInfo" time="0.147">
<failure message="Unexpected type DATE"
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
Unexpected type DATE
at
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.testGetTypeInfo(DatabaseMetaDataTest.java:2346)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120)
...
I will have to study this some more; I am not sure what is causing this
particular test to fail, and why it occurs only during the upgrade testing.
What do your errors and failures look like?+
> isNullable on ResultSetMetaData from DatabaseMetaData.getBestRowIdentifier
> values are opposite when there is no rows in ResultSet vs. when there is a
> row.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3181
> URL: https://issues.apache.org/jira/browse/DERBY-3181
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Reporter: Myrna van Lunteren
> Assignee: Danoja Dias
> Priority: Trivial
> Labels: derby_triage10_5_2
> Attachments: Derby-3181.diff, repro.java, testChange.diff
>
>
> With code like the following:
> DatabaseMetaData dmd = conn.getMetaData();
> ResultSet rs = dmd.getBestRowIdentifier(null,"APP","a",3,true);
> ResultSetMetaData rsmd = rs.getMetaData();
> int actualCols = rsmd.getColumnCount();
> for (int i = 0; i < actualCols; i++)
> {
> System.out.print("getColumnName: " + rsmd.getColumnName(i+1)
> + ", isNullable: ");
> System.out.println(rsmd.isNullable(i+1));
> }
> The printed values for isNullable returned are opposite of what they are when
> the getBestRowIdentifier call looks like this:
> ResultSet rs = dmd.getBestRowIdentifier(null,"APP","a",1,true);
> In the latter case, the values are:
> getColumnName: SCOPE, isNullable: 0
> getColumnName: COLUMN_NAME, isNullable: 1
> getColumnName: DATA_TYPE, isNullable: 0
> getColumnName: TYPE_NAME, isNullable: 1
> getColumnName: COLUMN_SIZE, isNullable: 0
> getColumnName: BUFFER_LENGTH, isNullable: 0
> getColumnName: DECIMAL_DIGITS, isNullable: 0
> getColumnName: PSEUDO_COLUMN, isNullable: 0
> In the first case, the values are:
> getColumnName: SCOPE, isNullable: 1
> getColumnName: COLUMN_NAME, isNullable: 0
> getColumnName: DATA_TYPE, isNullable: 1
> getColumnName: TYPE_NAME, isNullable: 1
> getColumnName: COLUMN_SIZE, isNullable: 1
> getColumnName: BUFFER_LENGTH, isNullable: 1
> getColumnName: DECIMAL_DIGITS, isNullable: 1
> getColumnName: PSEUDO_COLUMN, isNullable: 1
> The isNullable value should be stable.
> It's probably worthwhile verifying what the value *should* be in the first
> place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
