db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Commented: (DERBY-965) DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client
Date Fri, 03 Mar 2006 02:05:51 GMT
"Knut Anders Hatlen (JIRA)" <derby-dev@db.apache.org> writes:

> Knut Anders Hatlen commented on DERBY-965:
> ------------------------------------------
>
> Committed revision 382319.
>
> I didn't mark the issue as resolved because of the unanswered question
> about the phaseTester canon.

Thanks for committing this. I have uploaded another patch for the
phaseTester canon.

Dag

>
>> 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
>>      Fix For: 10.2.0.0
>>  Attachments: Main.java, derby965-v1.diff, derby965-v1.stat, derby965-v2.diff, derby965-v2.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
>

-- 
Dag H. Wanvik
Sun Microsystems, Database Technology Group (DBTG)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101

Mime
View raw message