Okay, suppose I know all about SQL Server 2000 design and what is and isn't good and I'm suddenly tasked with designing a MYSQL database tomorrow. Are there any guidelines for design that I should note? Obvious things are don't count on transactional/relational integrity to be enforced by the database and don't rely on a data structure that demands subselects for performance.
Other than that, doesn't seem to be an major limitations, but I won't know till I've built such a thing and thus I'm looking to the list to benefit from the MYSQL design experience of others. Thanks, -billb --------------------------------------------------------------------- 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
