Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 25868 invoked from network); 16 Sep 2009 23:00:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Sep 2009 23:00:19 -0000 Received: (qmail 66492 invoked by uid 500); 16 Sep 2009 23:00:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 66432 invoked by uid 500); 16 Sep 2009 23:00:19 -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 66424 invoked by uid 99); 16 Sep 2009 23:00:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2009 23:00:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2009 23:00:17 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7B5B8234C044 for ; Wed, 16 Sep 2009 15:59:57 -0700 (PDT) Message-ID: <2037290629.1253141997489.JavaMail.jira@brutus> Date: Wed, 16 Sep 2009 15:59:57 -0700 (PDT) From: "Rami Ojares (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756274#action_12756274 ] Rami Ojares commented on DERBY-499: ----------------------------------- Isn't it about time this issue is picked up? I mean boolean type is the simplest and most elementary of all datatypes. It seems quite amazing that this type would be too hard to implement whereas Derby has such obscure and useless types like XML? I mean it almost seems the world has gone mad! ;-) But seriously, why did you abandon the implementation Rick? I would be happy to help when time permits. > Expose BOOLEAN datatype to end users > ------------------------------------ > > Key: DERBY-499 > URL: https://issues.apache.org/jira/browse/DERBY-499 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: BooleanFS.html, BooleanFS.html, BooleanType.html, BooleanType.html, BooleanType.sxw, BooleanType.sxw, bug499.diff, bug499_doc.zip, bug499_jdk13tests.diff, bug499_jdk13tests_rev2.diff, bug499_rev2.diff, bug499_rev3.diff, bug499_rev4.diff, jdk131BooleanFailures.zip > > > Veaceslav Chicu started an email thread on 8 August 2005 titled "boolean type". He was disappointed that Derby doesn't support the ansi BOOLEAN datatype. On closer inspection, Derby does internally support this type but does not expose this support to end users. > Derby should let users declare table columns of type BOOLEAN. This should be an indexable datatype. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.