Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jhopkins@siop.org
Starting Member
1 Post |
 Posted - 2009-02-13 : 11:05:34
|
| I could use some advice I am a recent college graduate who is usually just programming. Now I am in charge of developing an online store and need to create the backend also. My problem is this we will be selling books and other products like shirts or backpacks. I really want to keep the products table seperate from the books table to avoid a ton of nulls for products that don't have the detail that books need. However, I need the relationship to be there for the order details. Is this where I implement a supertype - subtype? What are the drawbacks to this design? I was taught in school that we would hardly ever use this relationship but as I stare at my diagram it seems the only option as I can not have two foreign keys in the order details table when I am only inserting one type. Also how do I implement this design in sql server just define the relationship as one-to-one?Thanks in advance for any help on this |
|
|
|
|
|
Online store design