Three customer addresses in one table or in separate tables?

Posted by DR on Stack Overflow See other posts from Stack Overflow or by DR
Published on 2008-11-22T08:15:59Z Indexed on 2010/05/07 10:58 UTC
Read the original article Hit count: 151

In my application I have a Customer class and an Address class. The Customer class has three instances of the Address class: customerAddress, deliveryAddress, invoiceAddress.

Whats the best way to reflect this structure in a database?

  • The straightforward way would be a customer table and a separate address table.
  • A more denormalized way would be just a customer table with columns for every address (Example for "street": customer_street, delivery_street, invoice_street)

What are your experiences with that? Are there any advantages and disadvantages of these approaches?

© Stack Overflow or respective owner

Related posts about database

Related posts about oop