You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Andy Gumbrecht (JIRA)" <ji...@apache.org> on 2013/05/13 14:25:22 UTC

[jira] [Created] (DERBY-6223) Columns of type 'SMALLINT' cannot hold values of type 'BOOLEAN'

Andy Gumbrecht created DERBY-6223:
-------------------------------------

             Summary: 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: 10.10.1.1
         Environment: NA
            Reporter: Andy Gumbrecht
            Priority: Minor
             Fix For: 10.10.1.2


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira