You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2005/03/11 07:57:52 UTC

[jira] Closed: (DERBY-169) DatabaseMetaData calls related to changes made by others return incorrect values in Network Server mode.

     [ http://issues.apache.org/jira/browse/DERBY-169?page=history ]
     
Mamta A. Satoor closed DERBY-169:
---------------------------------

     Resolution: Fixed
    Fix Version: 10.0.2.1

The fix for this went in as Revision: 157015


> DatabaseMetaData calls related to changes made by others return incorrect values in Network Server mode.
> --------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-169
>          URL: http://issues.apache.org/jira/browse/DERBY-169
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.0.2.1
>     Reporter: Mamta A. Satoor
>     Assignee: Mamta A. Satoor
>      Fix For: 10.0.2.1

>
> I am working on getting updatable resultsets to work under Network Server mode. While running the test lang/updatableResultSet.java in Network Server mode, I came across following issue. DatabaseMetaData among other methods has 3 methods, othersUpdatesAreVisible, othersDeletesAreVisible and othersInsertsAreVisible. These 3 methods currently return true for TYPE_SCROLL_INSENSITIVE and TYPE_SCROLL_SENSITIVE when running in Network Server mode. They should be returning false for TYPE_SCROLL_INSENSITIVE and TYPE_SCROLL_SENSITIVE. The reason for that is 
> Derby does not yet implement scroll sensitive ResultSets and hence the 3 metadata calls mentioned above should return false. Also, scroll insensitive ResultSets by their definition do not see changes made by others and hence the 3 metadata calls should return false.
> The fix for this is very easy and requires changes in apache\derby\impl\sql\catalog\metadata_net.properties. 

-- 
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