• Coding

  • [DB Design] Where Should I Stick The ShippingDetails Table?

I'm almost done working on the model of my current project, but I still need to add shipping details. But I'm really not sure where it should go... Here's a link to the model: http://i54.tinypic.com/rbcpz7.jpg

In case you are wondering why the shipping details are needed, that is because the company I'm building the site for is a logistics company, which is hoping to provide a user-friendly auction website inside Lebanon. That includes online payment and delivery from the seller to the buyer; hence the need for shipping information.
I think it would be good if every user has his own shipping details or address other than the address, the shipping address would be filled upon doing an order or on sign up and saved for later use. You can create a table called shipping details and make a one to one relationship between the user and that table, where a user can have one shipping address and a shipping address belongs to one user, one to many can also exist depending on your requirements. Thats how I simply see it.
Alright, thanks Ayman. I won't add a ShippingDetails table to the database because I already got the addresses of the seller and the buyer.