[DERBY-965] DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: Network Client, Network Server
• Environment: Solaris 10, x86, Sun JDK 1.4.2
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 13/Feb/06 23:42
• Updated: 08/Aug/06 14:20
• Resolved: 03/Mar/06 20:16

Description

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.

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• relates to: DERBY-1252 Old clients with new server return wrong database metadata values for some methods