db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fischer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TORQUE-106) Use "boolean" sql type not "bit" sql type with MySQL
Date Thu, 01 Nov 2007 12:36:50 GMT

    [ https://issues.apache.org/jira/browse/TORQUE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539348

Thomas Fischer commented on TORQUE-106:

I do not understand the problem. The test project explicitly tests reading and writing booleans
and it definitely works with mysql 5.
Are you saying that BOOL would be more appropriate or are there any errors you encounter ?
If the latter is the case, please give details.
If the former is the case, what would be the advantage of using BOOL over BIT(1) ?

I am reluctant to change stuff if nothing is improved by it.
Even if the decision was made to change stuf, I'd not do it between RC's, unless it resolves
a bug.

> Use "boolean" sql type not "bit" sql type with MySQL
> ----------------------------------------------------
>                 Key: TORQUE-106
>                 URL: https://issues.apache.org/jira/browse/TORQUE-106
>             Project: Torque
>          Issue Type: Bug
>    Affects Versions: 3.2
>            Reporter: Will Glass-Husain
>         Attachments: mysqlpatch.patch
> In MySQL 5.0.3 the meaning of the BIT data type changed.  It used to be equivalent to
tinyint(1) but now it is a new bitwise datatype.  This means that when Torque generates SQL
files with a "bit" data type (mapped to the Java boolean) it is incorrect.
> I suggest that Torque map the Torque "bit" type to the MySQL "Boolean" type instead when
generating SQL.  See the reference from the MySQL manual below.
> http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html
> * BIT[(M)]
>       A bit-field type. M indicates the number of bits per value, from 1 to 64. The default
is 1 if M is omitted.
>       This data type was added in MySQL 5.0.3 for MyISAM, and extended in 5.0.5 to MEMORY,
InnoDB, and BDB. Before 5.0.3, BIT is a synonym for TINYINT(1).
>       A very small integer. The signed range is -128 to 127. The unsigned range is 0
to 255.
>       These types are synonyms for TINYINT(1). A value of zero is considered false. Non-zero
values are considered true: 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message