one to one relationship

[Anon]

I have 2 tables, ORDERS and SHIPPING. ORDERS table store information about the customers order and the SHIPPING table stores the shipping information(contact person and address). The 2 tables have a one-to-one relationship, that is for every ORDER, there can be only one SHIPPING.

Is it better to keep the data in one table, with the order and shipping info together
OR is it OK to separate them as below?
Any comments appreciated.

ORDERS

order_id (Primary Key)
customer_id
date
total_amount

SHIPPING

order_id (Foreign Key)
first_name
last_name
address
city
state
country
phone

[zhabala]

I think, that two tables solution is much more open for future enhancement when you will allow more than one shipment for one order.

Zdenek

[Anon]

IF you believe that there is ever a possability for a one-to-many relationship in the future then go with what youve got, otherwise the "rules" of database design say they should be in one table. But rules are there to be broken.

[ravikumar]

I think it is better to have two table.See this one depends upon the data u are storing. With respect to data, you need to do breakdown.

[Anon]

jhun,

there is absolutely nothing wrong with having two tables in a one to one relationship and can be preferable depending on the circumstances. It's called vertical partitioning and it's commonly done for performance enhancement.