db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
Date Tue, 15 Aug 2006 21:14:48 GMT
I reran the tests and got the same diffs, so I applied the changes and 
committed.

I suspect we have a version difference between the JCC drivers that I 
have been running and what is used in the regression tests.

David

Craig Russell (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428209 ]

>             
> Craig Russell commented on DERBY-1691:
> --------------------------------------
> 
> There is a tiny difference in the message text for:
> 
> com.ibm.db2.jcc.c.SqlException
> com.ibm.db2.jcc.a.SqlException
> 
> Is the difference something needs to be explained? 
> 
> Craig
> 
> 
>> jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
>> ----------------------------------------------------------------------
>>
>>                 Key: DERBY-1691
>>                 URL: http://issues.apache.org/jira/browse/DERBY-1691
>>             Project: Derby
>>          Issue Type: Bug
>>          Components: Test, Regression Test Failure
>>    Affects Versions: 10.2.0.0
>>         Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03
>>            Reporter: Rajesh Kartha
>>         Assigned To: David Van Couvering
>>             Fix For: 10.2.0.0
>>
>>
>> With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails.  The diff did not show anything
alarming, so I am guessing it
>> may be a master update. The test passed fine with DerbyClient
>> *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48
***
>> 466a467,474
>>> EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER.
>>> end clobTest54
>>> START: clobTest6
>>> EXPECTED SQLSTATE(null): Invalid position 0 or length 5
>>> EXPECTED SQLSTATE(null): Invalid position 1 or length -76
>>> EXPECTED SQLSTATE(null): Invalid position 1 or length -1
>>> EXPECTED SQLSTATE(null): Invalid position 0 or length 0
>>> FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
>> 468,475d475
>> < EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER.
>> < end clobTest54
>> < START: clobTest6
>> < EXPECTED SQLSTATE(null): Invalid position 0 or length 5
>> < EXPECTED SQLSTATE(null): Invalid position 1 or length -76
>> < EXPECTED SQLSTATE(null): Invalid position 1 or length -1
>> < EXPECTED SQLSTATE(null): Invalid position 0 or length 0
>> < FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
>> 775a776,782
>>> blobTest54 finished
>>> START: blobTest6
>>> EXPECTED SQLSTATE(null): Invalid position 0 or length 5
>>> EXPECTED SQLSTATE(null): Invalid position 1 or length -76
>>> EXPECTED SQLSTATE(null): Invalid position 1 or length -1
>>> EXPECTED SQLSTATE(null): Invalid position 0 or length 0
>>> FAIL -- unexpected exception:java.lang.NegativeArraySizeException
>> 777,783d783
>> < blobTest54 finished
>> < START: blobTest6
>> < EXPECTED SQLSTATE(null): Invalid position 0 or length 5
>> < EXPECTED SQLSTATE(null): Invalid position 1 or length -76
>> < EXPECTED SQLSTATE(null): Invalid position 1 or length -1
>> < EXPECTED SQLSTATE(null): Invalid position 0 or length 0
>> < FAIL -- unexpected exception:java.lang.NegativeArraySizeException
>> 789 del
>> < com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed
on object 'TESTBLOB' because there is an open ResultSet dependent on that object.
>> 789a789
>>> com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed
on object 'TESTBLOB' because there is an open ResultSet dependent on that object.
>> Test Failed.
>> *** End:   blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46
***
> 

Mime
View raw message