RE: [PHP] massive MySQL tables

You could normalize the db schema into several tables with fewer fields. This way though, you probably need to keep track of the transaction and commit the entire session or nothing at all. I hope you have split the form up into several pages. Personally, I hate when websites ask for tons of fields to be filled in on a single page. As a rule of thumb, any one page should not take more than 10-15 minutes max for a visitor to complete, IMHO. Johan www.pongworld.com tt php -----Original Message----- From: Justin French [mailto:justin@indent.com.au] Sent: Monday, October 08, 2001 4:23 PM To: php Subject: [PHP] massive MySQL tables Importance: High Hi all, Sorry for being slightly OT, but I'm working on a site with a large application form (84 fields) which people have to fill in. The form is rendering in the browser pretty quick (my first worry), but now I'm concerned that 85+ data fields in MySQL might create performance problems on the server. Is this likely? Most fields are "medium text" or "varchar", and will not need to be searched at all, so i'll prolly just index the two or three important ones, and leave it at that. If there is likley to be a performance hit, what other options will I have? Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net