db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6223) Columns of type 'SMALLINT' cannot hold values of type 'BOOLEAN'
Date Mon, 10 Mar 2014 18:27:46 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926005#comment-13926005

Romain Manni-Bucau commented on DERBY-6223:

I encouter this as well

> Columns of type 'SMALLINT' cannot hold values of type 'BOOLEAN'
> ---------------------------------------------------------------
>                 Key: DERBY-6223
>                 URL: https://issues.apache.org/jira/browse/DERBY-6223
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:
>         Environment: NA
>            Reporter: Andy Gumbrecht
>            Priority: Minor
>             Fix For:
> This minor issue is in relation to a bug at Liquibase (https://liquibase.jira.com/browse/CORE-1088)
that occurred due to the addition of the boolean type.
> Prior to the boolean type I am assuming that just about everyone would resort to using
smallint.Older databases that may have been machine created based on meta-data are not going
to be compatible with future code that will now assume boolean is the norm.
> The improvement I am suggesting is that when smallint columns are fed a boolean value
that '1' is accepted as 'true' and anything else 'false'  (0 would be a good idea), and likewise
for retrieval. Although technically correct, throwing an exception seems to be a touch aggressive
here as smallint is more than capable of storing a bit.

This message was sent by Atlassian JIRA

View raw message