http://www.mysql.com/doc/en/CHAR.html
Seems like that might bet be intended, but i don't know why. you might
try asking the developers. it seems though, that if the data you are
entering in that field is of a set size, like an SKU or some such, you
would save storage space, but retrieval would be unaffected, due to a
change from varchar to char.
T
On Tue, 20 May 2003 Gearmorer@stripped wrote:
> I did use the MySQL General list, but no one responded. I presume it must not
> be a
> big problem. And BTW, I did try the same command:
> create table products_tmp as select * from products_tbl;
> at the Command Prompt as you suggested, but it came out the same way.
>
> The data types were changed from varchar(yy) in the original table, to
> char(yy) in the newly created table. So I guess I'll do like everyone else
> and ignore it.
>
> Garth Armorer
> kiskedee@stripped
>
