Re: VARCHAR/CHAR question...

Michael: this is correct...only with mysql...and the reason for this is that any speed and storage advantages you may have gained by specifying a field to be CHAR is lost if in the same row you have another field of type VARCHAR, so they both may as well be VARCHAR... ...it really makes little difference...in terms of storage, if you really plan to have so many records that this would be of consequence, you are probably better off going with a databa$e like oracle... That is the way I understand it anyways... Luis --- Michael Zornek <mzornek@seyboldreports.com> wrote: > 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 > __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/