db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject [PATCH] (DERBY-169) DatabaseMetaData calls related to changes made by others return incorrect values in Network Server mode.
Date Wed, 09 Mar 2005 16:55:22 GMT
On Wed, 9 Mar 2005 08:41:52 +0100 (CET), Mamta A. Satoor (JIRA)
<derby-dev@db.apache.org> wrote:
> 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:
>    Reporter: Mamta A. Satoor
> Assigned to: Mamta A. Satoor
> 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
> 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

Here is a very simple fix for the bug with the tests, I have run the
test suites and the fix hasn't caused any failures.

svn stat output
M      java\engine\org\apache\derby\impl\sql\catalog\metadata_net.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\metadataJdbc20.java
M      java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\metadataJdbc20.out
M      java\testing\org\apache\derbyTesting\functionTests\master\metadataJdbc20.out
M      java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\metadataJdbc20.out


View raw message