I'm just guessing here, but I suppose most of the char(1) fields are y/n fields. If that's the case you should consider using a single BIGINT and flag those bits instead. That would considerably reduce the size of the table on one hand and I guess it should improve things speed-wise as well.
Obviously, my whole theory stands on a supposition, so I might be wrong in suggesting this. Bogdan "Greer, Darren (MED)" wrote: > id int(11) NOT NULL - Auto Increment > address char(90) NOT NULL > status char(2) NOT NULL > country char(2) > state char(2) > areacode char(3) > ...about 40 char(1) fields. --------------------------------------------------------------------- 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
