Mark Chalkley writes:
> According to the MySQL manual (section 7.7.1), CHAR columns defined to be greater
>than 3 chars in length are converted to type VARCHAR. I understand the space
>efficiency issues involved here, but when the column is used in an index, doesn't
>that impose a performance penalty? Or does MySQL handle indexes in a manner
>different from other RDBMS, so that this doesn't happen?
>
> Thanks,
>
> Mark Chalkley
>
> P.S. If this message ends up duplicated, I apologize. I sent it a couple hours ago
>and it hasn't shown up on the list yet, so I'm resending it.F
>
>
Hi!
The above is true only if a table is already of the variable length,
which imposes performance penalty per se.
Regards,
Sinisa
____ __ _____ _____ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____
^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^
/*/ \*\ Developers Team
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
