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

Thomas Vandahl commented on TORQUE-106:
---------------------------------------

I remember a problem with bit columns in the runtime test of Torque against 
MYSQL-5 which could be solved by using a new MYSQL JDBC driver, version 5.0 or 
higher. Could you please check if that applies to your case, too?

> 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).
>     
> *  TINYINT[(M)] [UNSIGNED] [ZEROFILL]
>       A very small integer. The signed range is -128 to 127. The unsigned 
> range is 0 to 255.
>    
> * BOOL, BOOLEAN
>       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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to