-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill Bernat wrote:
| 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
Not true if you're using the InnoDB table type. See the www.innodb.com,
and the latest MySQL server manual.
| and don't rely on a data structure that demands subselects for
performance.
Sub-selects generally aren't performant ;)
In general, use standard normalization, but don't go crazy with it (like
4th or 5th normal form), put indexes where they belong and you'll be
okay with MySQL.
-Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAj0P4X8ACgkQlyjUJM+7nP4xBwCdHU2lp212E5yziZkh0X0CvQy9
5y4AoIWmCveYN5FW+JkExu/x1kTEEuQN
=T3xV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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
