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.
i have two tables:
1) Users
2) Scenarios
Relation between them can be described as:
User can have 0 or more Scenarios
Scenario must be associated with exactly one User
One way is to create User_Scenario_rels and use ID from users and scenarios table to create relationships. But is this the best practice? Is this 1 to many relationship?
This is a “one to many” relationship – one scenary has one user, one user has many scenarios.
It’s commonly modeled by a “user_id” column on the scenario table.
In terms of database design as practised in the field, there’s no distinction between “a user has 0 or more scenarios” and “a user has 1 or more scenarios”; in theory, if you wanted to impose the rule that all users MUST have at least 1 scenario, you would implement a constraint.