db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server
Date Mon, 06 Feb 2006 16:01:49 GMT
Knut Anders Hatlen wrote:

>"Kathey Marsden (JIRA)" <derby-dev@db.apache.org> writes:
>
>  
>
>>    [ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12365237
] 
>>
>>Kathey Marsden commented on DERBY-821:
>>--------------------------------------
>>
>>Bryan posted some questions on the list.  I put the link here for reference.
>>
>>http://www.nabble.com/DERBY-821-comments-t1065371.html
>>
>>I have not had an opportunity to review the patch but hope to do so
>>tomorrow.  I was wondering if you had tested 10.1/10.2 client/server
>>combinations.
>>    
>>
>
>I have run derbynetclientmats on trunk with only server changes
>applied (checking the combination of new server/old client) and on
>10.1 with only client changes applied (new client/old server). No
>failures.
>
>  
>
>>If there is special logic needed for JCC, I am
>>guessing it might also be needed for older clients and ODBC, but
>>just a guess as I have not yet looked at the patch.
>>    
>>
>
>Do you know what the ODBC clients identify themselves as? I found
>these types of clients in AppRequester.java:
>
>  protected static final int UNKNOWN_CLIENT = 0;
>  protected static final int JCC_CLIENT = 1;
>  protected static final int CCC_CLIENT = 2;		// not yet supported.
>  protected static final int DNC_CLIENT = 3;		// derby net client 
>
>  
>
ODBC is CCC.   The // not yet supported comment must be old.  Army would
be able to say better if any change is needed for ODBC.  It may just be
fine.




Mime
View raw message