Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14813 invoked from network); 13 Feb 2006 14:43:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Feb 2006 14:43:51 -0000 Received: (qmail 44334 invoked by uid 500); 13 Feb 2006 14:43:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 44303 invoked by uid 500); 13 Feb 2006 14:43:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 44294 invoked by uid 99); 13 Feb 2006 14:43:50 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 06:43:47 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 0218EDF for ; Mon, 13 Feb 2006 15:43:27 +0100 (CET) Message-ID: <702071389.1139841807006.JavaMail.jira@ajax.apache.org> Date: Mon, 13 Feb 2006 15:43:27 +0100 (CET) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-965) DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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