Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <15053792.5481271102270789.JavaMail.jira@thor>
Date: Mon, 12 Apr 2010 15:57:50 -0400 (EDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4613) Make client driver treat BOOLEAN
 columns the same way as the embedded driver does.
In-Reply-To: <13524577.2051271096149759.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-4613:
---------------------------------

    Attachment: derby-4613-fs.html

Attaching functional spec for the work to be done here.

> Make client driver treat BOOLEAN columns the same way as the embedded driver does.
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-4613
>                 URL: https://issues.apache.org/jira/browse/DERBY-4613
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.6.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-4613-fs.html
>
>
> The only operation currently allowed on BOOLEAN columns is to select them from the system tables. For instance, the following query selects BOOLEAN values:
>     select systemalias from sys.sysaliases;
> There are discrepancies in how the embedded and client drivers handle these BOOLEAN columns. The embedded behavior is correct and the client behavior should conform. I will attach a spec describing what needs to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira