db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
Date Thu, 17 Aug 2006 23:39:22 GMT
David Van Couvering wrote:
> Since failures in DerbyNet seem to be part of the overall regression
> failures that people hit, it would be great if the db2jcc jar files were
> just available rather than having to go through the process of
> registering and installing Cloudscape to get the jars.
> 
> Any reason these can't be checked into tools/java, as long as they are
> not getting distributed in the release?  Or are there legal constraints?

Software under one of the Category A licenses listed at
http://www.apache.org/legal/3party.html may be checked into an ASF svn
repo. I don't think these qualify.

 -jean

> David
> 
> David Van Couvering (JIRA) wrote:
> 
>>     [
>> http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736
>> ]             David Van Couvering commented on DERBY-1691:
>> --------------------------------------------
>>
>> Sigh...  I'll look at this. Really, it passed on my platform.  Craig,
>> this is the *last* time I'll commit a patch for you :)
>>
>>> 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