Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 57296 invoked from network); 6 Feb 2007 17:15:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2007 17:15:29 -0000 Received: (qmail 96652 invoked by uid 500); 6 Feb 2007 17:15:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 96623 invoked by uid 500); 6 Feb 2007 17:15:34 -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 96604 invoked by uid 99); 6 Feb 2007 17:15:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 09:15:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 09:15:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 37BF27142BF for ; Tue, 6 Feb 2007 09:15:06 -0800 (PST) Message-ID: <18227215.1170782106225.JavaMail.jira@brutus> Date: Tue, 6 Feb 2007 09:15:06 -0800 (PST) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA In-Reply-To: <26434978.1169235570187.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470647 ] Daniel John Debrunner commented on DERBY-2260: ---------------------------------------------- It was just a safety check to ensure that a NULL value was not being returned for precision. Probably not required (before the XML changes) since a precision of zero was never returned. We can assume that a NULL will be returned as zero. Now with the addition of an XML type you need to test that a NULL value is being returned, checking for a precision of 0 is not enough. So for the XML case you need ensure that rs.wasNull() returns true. > DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA > ----------------------------------------------------------------------------------- > > Key: DERBY-2260 > URL: https://issues.apache.org/jira/browse/DERBY-2260 > Project: Derby > Issue Type: Bug > Affects Versions: 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0 > Reporter: Daniel John Debrunner > Assigned To: Saurabh Vyas > Priority: Minor > > PRECISION column for VARCHAR FOR BIT DATA is returned as 32762, but maximum precision is 32672 (6 & 7 swapped). > ij> create table z (a varchar(32672) for bit data); > 0 rows inserted/updated/deleted > ij> create table z2(a varchar(32673) for bit data); > ERROR 42611: The length, precision, or scale attribute for column, or type mapping 'VARCHAR (32673) FOR BIT DATA' is not valid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.