db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: GetTypeInfo fails with ibm16 on Linux
Date Fri, 08 Feb 2008 19:26:37 GMT
Manjula Kutty wrote:
> The getTypeInfo Fails with ibm16 while running the UpgradeTests. Here is 
> junit stack trace
> 1) 
> testGetTypeInfo(org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest)junit.framework.AssertionFailedError:

> Column nullability do not match for column 16 expected:<1> but was:<0>
> at org.apache.derbyTesting.junit.JDBC.assertNullability(JDBC.java:741)
> at 
> org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.assertMetaDataResultSet(DatabaseMetaDataTest.java:2348)
> at 
> org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.testGetTypeInfo(DatabaseMetaDataTest.java:2230)

> Does it look like derby issue or a jvm problem?

Looks like a jvm issue:

  DatabaseMetaDataTest passes on the same vm standalone.

  This test passes on other virtual machines.

  The expected and correct nullability for the column is non-null which 
is a zero in the assert above. The the engine is returning the correct 
value (0) but the assert is expecting (1).

  At line 2220 of DatabaseMetaDataTest is where the expected value for 
this column is set:
   ODBC_COLUMN_NULLABILITY[16 - 1] = false;

The false would map to a zero in the expected value. It's as though that 
line was not being executed by the virtual machine.


View raw message