List:General Discussion« Previous MessageNext Message »
From:Robert M (Bob) Bartis Date:May 19 2006 1:01pm
Subject:RE: Is This A Redundant Info Example?
View as plain text  
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.

Bob

-----Original Message-----
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?


[snip]
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.
[/snip]

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
Thread
Is This A Redundant Info Example?Mark Sargent19 May
  • Re: Is This A Redundant Info Example?Martijn Tonies19 May
    • Re: Is This A Redundant Info Example?sheeri kritzer19 May
  • Re: Is This A Redundant Info Example?Martijn Tonies19 May
  • Re: Is This A Redundant Info Example?John Hicks19 May
RE: Is This A Redundant Info Example?Jay Blanchard19 May
RE: Is This A Redundant Info Example?Bob)19 May
RE: Is This A Redundant Info Example?Jay Blanchard19 May
  • Re: Is This A Redundant Info Example?sheeri kritzer19 May
  • Re: Is This A Redundant Info Example?Martijn Tonies20 May