Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 81537 invoked from network); 21 Nov 2005 17:12:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Nov 2005 17:12:53 -0000 Received: (qmail 35908 invoked by uid 500); 21 Nov 2005 17:12:29 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 35631 invoked by uid 500); 21 Nov 2005 17:12:27 -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 35571 invoked by uid 99); 21 Nov 2005 17:12:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2005 09:12:26 -0800 Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.36] (HELO brmea-mail-4.sun.com) (192.18.98.36) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2005 09:13:58 -0800 Received: from phys-d3-ha21sca-2 ([129.145.155.165]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id jALHC4D7019975 for ; Mon, 21 Nov 2005 10:12:04 -0700 (MST) Received: from conversion-daemon.ha21sca-mail1.sfbay.sun.com by ha21sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IQB00401EC5H8@ha21sca-mail1.sfbay.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Mon, 21 Nov 2005 09:12:35 -0800 (PST) Received: from [129.144.89.176] (d-sfo07-89-176.SFBay.Sun.COM [129.144.89.176]) by ha21sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IQB00K4HEGZLP@ha21sca-mail1.sfbay.sun.com> for derby-dev@db.apache.org; Mon, 21 Nov 2005 09:12:35 -0800 (PST) Date: Mon, 21 Nov 2005 09:12:16 -0800 From: Rick Hillegas Subject: Re: [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users In-reply-to: <4381FD30.8030203@amberpoint.com> To: derby-dev@db.apache.org Message-id: <4381FFF0.7060301@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) References: <2015076743.1132591182460.JavaMail.jira@ajax.apache.org> <4381FD30.8030203@amberpoint.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Bryan, Nope. This does not affect getBoolean() and setBoolean() on other datatypes. Cheers, -Rick Bryan Pendleton wrote: >> I have attached a thin functional specification describing expected >> SQL and JDBC behavior for the re-enabled BOOLEAN datatype. > > > Are there any changes to the way that ResultSet.getBoolean() > and PreparedStatement.setBoolean() work for data types *other* > than the boolean data type? > > thanks, > > bryan > >