db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: Mixed client sever and upgrade and compatibility testing with Junit Tests
Date Thu, 16 Dec 2010 13:50:05 GMT
Kathey Marsden <kmarsdenderby@sbcglobal.net> writes:

> I have not had a chance to look at the tests but I think the tests are
> clever but Derby DatabaseMetaData is not clever enough to know it
> should not return BOOLEAN in soft upgrade mode, so the tests are
> trying to use it because they think it is available when it is not.
> The derbyTesting.jar from 10.6 should run clean on a soft upgraded
> database using 10.7 product jars, just like any 10.6 application.   Of
> course the new functionality in the 10.7 derbyTesting.jar should not
> work and so sensible that it has failures.
> I did verify the DatabaseMetaData getTypeInfo() bug and filed:
> https://issues.apache.org/jira/browse/DERBY-4946

Right, I did not think of that as a bug initially, but reconsidering it
I agree that is probably wrong behavior on Derby's part: metadata should
reflect the present capabilities (in casu the soft upgraded state).


View raw message