db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-965) DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client
Date Thu, 23 Feb 2006 15:35:39 GMT
     [ http://issues.apache.org/jira/browse/DERBY-965?page=all ]

Dag H. Wanvik updated DERBY-965:
--------------------------------

    Attachment: derby965-v1.stat
                derby-992-1.diff

* The patch, derby965-v1.{stat,diff}, corrects the server data to the correct values, 
retaining the encoding used on the server side. The new values
(metadata_net.properties) now reflect the capabilities of the
server+network client driver::

        '1003,1007,1008;1004,1007;1005'
i.e. decoded:
     
        TYPE_FORWARD_ONLY,CONCUR_READ_ONLY,CONCUR_UPDATABLE;
        TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY
        TYPE_SCROLL_SENSITIVE

DERBY-775 (client SUR) will be adding CONCUR_UPDATABLE to the second
line later.

* The client's parsing and decoding has been changed to comply with
this encoding style and now gives the correct result
(changes in getMetaDataInfoInt_SupportsResultSetConcurrency).

* This patch should not give upgrade problems, in that an older client
against a new server will give the same (wrong) results as before when
trying to interpret type as concurrency. A new client against and old
server will work, but give wrong results, although wrong in a
different way from before. cf. the analysis of feb-13
above. Presumably, apps relying on this method would have failed
always, so the changed result should not be too serious.

* Tests of this method has been added to metadata_test.java and
embedded and derby network client canons have been
updated.

* NOTE: Unfortunately, derbynetmats running the JCC client seems to
have the same problem (it returns false for all type, concurrency
combinations), so I had to make derbynetmats skip these new tests for
that driver.

* derbyall has been run successfully on Sun's 1.4.2 VM (modulo errors
seen in regression test).

* For the other canons (non-1.4.2 VMs), I have inserted the expected
results, but not verified them.

* I noticed the canon of phaseTester also contain metadata_test
output, but I did not update this test's canon, as I am not familiar
with how it should be updated. I'd appreciate advice on that.


> DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network
client
> -------------------------------------------------------------------------------------------
>
>          Key: DERBY-965
>          URL: http://issues.apache.org/jira/browse/DERBY-965
>      Project: Derby
>         Type: Bug
>   Components: Network Server, Network Client
>     Versions: 10.2.0.0
>  Environment: Solaris 10, x86, Sun JDK 1.4.2
>     Reporter: Dag H. Wanvik
>     Assignee: Dag H. Wanvik
>     Priority: Minor
>  Attachments: Main.java, derby-992-1.diff, derby965-v1.stat
>
> The DatabaseMetaData method supportsResultSetConcurrency erroneously
> returns false on the network client for all arguments combination, cf
> the attached repro program. The embedded client returns correct
> results, viz the output:
> org.apache.derby.jdbc.ClientDriver:
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_UPDATABLE: false
> org.apache.derby.jdbc.EmbeddedDriver:
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_READ_ONLY: true
> SupportsResultSetConcurrency: TYPE_FORWARD_ONLY,CONCUR_UPDATABLE: true
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_READ_ONLY: true
> SupportsResultSetConcurrency: TYPE_SCROLL_INSENSITIVE,CONCUR_UPDATABLE: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_READ_ONLY: false
> SupportsResultSetConcurrency: TYPE_SCROLL_SENSITIVE,CONCUR_UPDATABLE: false
> Presumably, this is wrong in released versions as well.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message