Knut Anders Hatlen <[email protected]> writes:

> Knut Anders Hatlen <[email protected]> writes:
>
>> Kathey Marsden <[email protected]> writes:
>>
>>> On 12/13/2010 11:58 AM, Rick Hillegas wrote:
>>>>
>>>> I see that Ole ran this test on 10.5.3 and 10.6.1. Ole no longer
>>>> works on Derby. As you note, no-one has run that test on 10.6.2 or
>>>> 10.7.1.
>>>>
>>> Is there someone that has access to these tests that can run them now
>>> that Ole is gone or is it just one more bit of testing we don't do
>>> anymore?  It would be nice to know we are compliant for  a release off
>>> trunk.
>>
>> I found the instructions for running these tests and have started
>> them. So if everything goes well, we'll have the results shortly.
>
> It didn't go all that well... Here's what the report says:
>
> batchUpdate.out:     passed: 68
> callStmt.out:        passed: 1,580; failed: 20
> connection.out:      passed: 36
> dateTime.out:        passed: 152
> dbMeta.out:          passed: 940
> escapeSyntax.out:    passed: 324
> exception.out:       passed: 56
> prepStmt.out:        passed: 1,072; failed: 12
> resultSet.out:       passed: 452; failed: 4
> rsMeta.out:          passed: 84
> stmt.out:            passed: 132
> Total time: 09:58:28 
>
> I haven't looked at all the failures yet. Those I have looked at appear
> to happen because our meta-data now says that we support BOOLEAN,
> whereas the database schema created by the test itself contains
> workarounds for Derby's lack of support for BOOLEAN (like using SMALLINT
> columns instead of BOOLEAN columns). So I think there are some changes
> required for the DDL and DML scripts that create the database schema in
> order to make the test run successfully, but I haven't found anything
> that appears to be a Derby problem yet.

After I have updated DDL, DML and stored procedure signatures to use
boolean instead of smallint/short, I see 24 failures in
PreparedStatement and 32 failures in CallableStatement. These are all
variants of DERBY-4964 (client only) and DERBY-4965 (client and
embedded). I've added the "deviation from standard" flag to the bug
reports.

-- 
Knut Anders

Reply via email to