Is there anyway I can get the test to run in my setup? I will look into fixing Derby Client problem.

We could checkin your test, with an exclude added to DerbyNetClient.exclude. I will file a bug for DerbyClient and once I resolve the issue, I could enable the test for DerbyNetClient framework. Any other ideas?

Satheesh

Daniel John Debrunner wrote:
Satheesh Bandaram wrote:

    
I have briefly looked at the large test... Would it be ok to modify the
test next week, after the release? The patch corrects the problem being
reported and I will run the regular tests. I will keep the bug open
until a test is added here..
      
I'll look into adding the test cases.
    

I've been adding the setXXX with executeBatch() that currently work with
embedded into the parameterMapping test. Seems to work fine on embedded
and JCC, but with the Derby client the test just seems to stop after a
setByte() and executeBatch() against VARCHAR FOR BIT DATA. So the good
thing is the additional testing may have uncovered a bug, the bad thing
is I can't check in the test changes until it doesn't cause problems on
the client.

Dan.




  

Reply via email to