List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:June 4 2000 5:40pm
Subject:Re: MySQL-Bug or Feature when using CHAR(...) and VARCHAR(...)
simult aneaously??
View as plain text  
At 7:20 PM +0200 2000-06-04, Joosten, Juergen wrote:
>Hello,
>
>I'm quite confused about one thing.
>
>When I declare one or more rows to have datatype CHAR(...) all is ok.
>But when I additionally declare at least one row to have datatype VARCHAR,
>then all these rows have datatype VARCHAR in the end - the rows declared as
>CHAR(...), too.
>Even more confusing for me is the fact that rows declared as CHAR(4) or less
>(CHAR(3),...) keep their datatype.
>
>I'm not quite sure if this is a bug or a feature (performance reasons?), but
>I'd really like to have rows that I declared as CHAR(...) to keep its
>datatype.
>
>Can someone help me with this?


This is explained in the MySQL Reference Manual:

http://www.mysql.com/php/manual.php3?section=Silent_column_changes

-- 
Paul DuBois, paul@stripped
Thread
MySQL-Bug or Feature when using CHAR(...) and VARCHAR(...) simultaneaously??Juergen Joosten4 Jun
  • Re: MySQL-Bug or Feature when using CHAR(...) and VARCHAR(...)simult aneaously??Paul DuBois4 Jun