Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When designing a table for a many to many relations ship 1 sides primary key will come to the [M] side the middle table, my current middle table is
Salesline : Itemid(PK), SOId(PK), userid(PK)
or
Salesline : Itemid(PK), SOId(PK),
userid_salesorder(PK) , // links to the salesorder.userid attribute
userid_item(PK) // links to the item.userid attribute
Which is the correct way ?
Looks like the natural realtionships between your entities are:
I would recommend to break the realtionship between the User and Item tables and to move the quantity of the particular item ordered to the SalesLine table. User, SalesOrder and Item should have simple, possibly surrogate, primary key. The primary key of the SalesLine may be composite, consisting of the foreign key to the SalesOreder table and, say, a line number within the order.