Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003

    customer and invoice address 1:1


    I have a CUSTOMER table that has customer name, address, tel etc. The customer address is not the same as the invoice address, but each customer will only have one invoice address, therefore a 1:1 relationship.

    Is it correct to put the two addresses in the same table, that is, custName, custAdd, custTel etc., and invName, invAdd, invTel etc. or should this be two tables, if so what are the advantages of this.

    Many thanks,


  2. #2
    Join Date
    Apr 2002
    Toronto, Canada
    it's pretty much a wash

    how often do you run a query that needs customer name plus invoice address (i.e. non-key fields from both tables)? that's how often you do a join, which is less efficient

    how many times does the invoice address differ from the physical address (i.e. require a row in the second table)? that's how many "extra" rows you will have

    on the other hand, with null fields in one table, you won't really take any "extra" space (except for null bits, which are negligible), and you'll save yourself the bother of doing a join

    like i said, it's pretty much a wash, do it whichever way makes sense to you


  3. #3
    Join Date
    Sep 2003


    Hi Rudy,

    Thanks for the help and advice,


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts