Bad design that violates basic DB design checks. Redundant information will become a major
problem for you going forward. Unless you have hard and fast performance issues they
require it, just don't do it:-)
Create a single table that contains customer info and reference the information using
Foreign keys in your other tables that require customer information.
From: Jay Blanchard [mailto:jblanchard@stripped]
Sent: Friday, May 19, 2006 8:57 AM
To: Mark Sargent; mysql@stripped
Subject: RE: Is This A Redundant Info Example?
Why have customer info in both? Delivery and Billing info makes sense,
but why the redundant info in both? Anyone got views on this? Do/would
you do it differently, and could you tell us why? Cheers.
It is bad database design IMHO.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1