Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42FA93D2.1060309@sbcglobal.net>
Date: Wed, 10 Aug 2005 16:54:58 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [VOTE] Support the ANSI-SQL standard BOOLEAN datatype.
References: <42FA5C14.8030605@sun.com> <42FA84A7.9030904@sbcglobal.net>
 <42FA8C5D.6000902@sun.com>
In-Reply-To: <42FA8C5D.6000902@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Rick Hillegas wrote:

> Hi Kathey,
>
> I have found two tests which look like they monitor datatype
> conformity for PreparedStatements and ResultSets:
>
>   jdbcapi/parameterMapping.java
>   jdbcapi/resultSet.java
>
> BOOLEAN support was removed from these tests and I intend to put it
> back in. This will verify that you can use jdbc to set BOOLEAN
> parameters and retrieve BOOLEAN columns.
>
> Are there other jdbc tests which I should amend? What other client
> behavior should I track down? 

I think you will find that  Network Server sends BOOLEAN as a SMALLINT 
because at least at the time it was written there was no BOOLEAN type in
the protocol specification.  Maybe that has changed. You could check the
specs at  http://www.opengroup.org/dbiop.

I think this means that as things are now, the client  ResultSet
Metadata will show SMALLINT instead of BOOLEAN,  getString  will show 1
or 0   instead of true/false and any other jdbc differences between
BOOLEAN and SMALLINT will exist.   If that is the way it would stay it
would make for a really awkward differences between  embedded and client.

Watch out just checking that tests pass, because the test harness even
still has code I think to mask out this difference so that tests will
appear to pass.

Kathey