Re: VARCHAR/CHAR question...

This doesn't sound correct at all. I've spoken to an IBMer about DB2, and he confirms this is not the case in DB2. I don't see why MySQL would do something quite so odd, especially considering that it takes more processor time to work with VARCHARs than CHARs. This is the prime reason it is usually recommended that one only use VARCHAR where it is absolutely necessary (for example, if a column can have a length of 128, but it can also only contain only a few bytes, then forcing a CHAR is a bit much). "Michael Zornek" <mzornek@seyboldreports.com> wrote in message news:a05001915b656d2910943@[38.241.81.150]... > I'm new to PHP, and I found a questionable line in a book I'm reading > (BEGINING PHP 4), in the MySQL chapter page 390 it says: > > " A final note on VARCHAR/CHAR type fields; if your table has at > least one VARCHAR field all character fields are converted to VARCHAR > type even if you define them otherwise." > > That doesn't seen fair or correct. > > Anybody have any comments or suggestions. I'll gladly follow this in > designing my new DB but am suprised to read it. > > mike > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >