As a general rule, it's been my experience with MySQL that well-designed queries on properly indexed tables yield good performance. There are, of course, exceptions to the rule where performance may be improved by moving a portion of a query into the application and times when the execution of a query may need to be coerced.
The biggest risk I've seen in not using foreign key constraints is the potential for orphans. Programmatically, inserts are about the same but, without cascading deletes, additional programming is required to remove related records which may lead to errors. However, orphans are easily detected with a simple query and, with good programming practice and testing procedures, just as easily prevented. Once upon a time, CPU cycles, memory and disk space mattered. -Terence M. Bandoian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
