DO NOT REPLY [Bug 26535] New: - [sql] tries to alter tinyint to bit repeatedly

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26535>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26535

[sql] tries to alter tinyint to bit repeatedly

           Summary: [sql] tries to alter tinyint to bit repeatedly
           Product: Commons
           Version: 1.0 Alpha
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Sandbox
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: gus.heck@olin.edu


The alter code works wonderfully so far, this is the first issue I have had with
it. I have a class which is being persisted into Mysql 4.0.14-stable. one of the
fields is a boolean field. Torqueschema  generates a type of BIT for this field.
When the sql alter code sent this type to mysql mysql interpreted BIT as TINYINT
and merrily obliged to make the collumn. The problem is that now every time
builder.alterDatabase( db, existing, doDrops, true ); looks at the TINYINT
column and compares it to the BIT column in the torque schema it issues the
following alter statement:

ALTER TABLE ContactInfoBase
    MODIFY obsolete BIT NULL ;

This succeeds, but the column type is (of course) still TINYINT and so this
cycle will repeat indefinately. This is only done when my PersistenceHelper
class is first loaded, but it generates needless sql executions, which could
become really annoying for other usages.

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