[Dbix-class] test failures in DBIx::Class v0.06999_03

[Carl Franks]

On 27/06/06, Matt S Trout <dbix-class at trout.me.uk> wrote:
> Brandon Black wrote:
> > On 6/27/06, Matt S Trout <dbix-class at trout.me.uk> wrote:
> >> Carl Franks wrote:
> >>> t\71mysql.......................NOK 5
> >>> #   Failed test 'columns_info_for - column data types'
> >>> #   in t\71mysql.t at line 71.
> >>> #     Structures begin differing at:
> >>> #          $got->{charfield}{data_type} = 'VARCHAR'
> >>> #     $expected->{charfield}{data_type} = 'CHAR'
> >>> # Looks like you failed 1 test of 5.
> >> Argh. I'm sure we changed this because of test failures for somebody else. Can
> >> anybody else with MySQL run this please and see if it's a uniform failure?
> >>
> >
> > Its not.  I just tested the CPAN tarball of 0.06999_03 here and got
> > success on 71mysql.t.  Relevant environmental details:
>
> Right. Sod it. Test disabled until we figure out how to deal with this
> properly. I'm not blocking a release because either mysql or its DB is retarded.

woohoo! - "Silent Column Specification Changes" :)
http://dev.mysql.com/doc/refman/5.0/en/silent-column-changes.html

If any column in a table has a variable length, the entire row becomes
variable-length as a result. Therefore, if a table contains any
variable-length columns (VARCHAR, TEXT, or BLOB), all CHAR  columns
longer than three characters are changed to VARCHAR columns.

These occur prior to MySQL 5.0.3. As of 5.0.3, an error occurs if a
column cannot be created using the specified data type.

Agreed, mysql is retarded