db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Tue, 07 Feb 2006 08:09:47 GMT
"Kathey Marsden (JIRA)" <derby-dev@db.apache.org> writes:

>     [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12365387 ]

>
> Kathey Marsden commented on DERBY-821:
> --------------------------------------
>
> I looked at the server side Changes:
> Regarding the JCC check in DRDAStatement, Bryan said
>>  perhaps it's worth
>> looking at this a little while longer, to see if there is a way to handle
>> this without having to add the session pointer to the database object; maybe
>> you could instead arrange to pass the session pointer as an argument when
>> you call isRSCloseImplict?
>
> I think it would be better to just have it take a boolean and
> centralize the differences for AppRequesters in AppRequester.java
> with supportXXX() methods there.  In this case, If we can get the
> JCC side fixed the condition will have to be modified further to
> include version info.  It is best to have that all in one place I
> think.

I agree. For now, I will treat CCC the same way as JCC (i.e., don't
change the behaviour).

> There was a question on negative testing for protocol.  There is a
> test testProtocol.java which has a file protocol.tests where you can
> put tests for protocol sequences that will never actually be sent
> from the client.

Thanks! I'll have a look at that test.

-- 
Knut Anders


Mime
View raw message