db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Assigned: (DERBY-173) For the concurrency of ResultSet, Network Server should not send the concurrency of Statement.
Date Tue, 22 Mar 2005 14:40:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-173?page=history ]

Mamta A. Satoor reassigned DERBY-173:
-------------------------------------

    Assign To: Mamta A. Satoor

> For the concurrency of ResultSet, Network Server should not send the concurrency of Statement.
> ----------------------------------------------------------------------------------------------
>
>          Key: DERBY-173
>          URL: http://issues.apache.org/jira/browse/DERBY-173
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.0.2.1
>     Reporter: Mamta A. Satoor
>     Assignee: Mamta A. Satoor
>      Fix For: 10.1.0.0

>
> I am working on getting updatable resulset functionality to work under Network Server.
One issue that I found is Network Server sends the concurrency of the Statement object when
it really needs to send the concurrency of the Resultset. This was ok in the past because
CONCUR_READ_ONLY was the only concurreny supported by Derby. But, now with the support of
CONCUR_UPDATABLE, it is possible that the concurrency of ResultSet might not be same as the
Statement object. Hence, Network Server should send the concurrency of the ResultSet object
if that is what the protocol calls for.
> The fix for this is localized in java\drda\org\apache\derby\impl\drda\DRDAConnThread.java.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message