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] Created: (DERBY-965) DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client
Date Mon, 13 Feb 2006 14:43:27 GMT
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 Client  
    Versions: 10.2.0.0    
 Environment: Solaris 10, x86, Sun JDK 1.4.2
    Reporter: Dag H. Wanvik
    Priority: Minor


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