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 DB tables, ACTIVITY and USER.
In the ACTIVITY table I have 3 fields AssignedTo, CreatedBy and LastModifiedBy that need to be related (1 to many, so that a user can create, modify and be assigned to many activities) with UserId field and primary key of the USER table.
Is it a good practice to create three different relationships between the two tables, all three connected with the primary key, in this case UserId, of the parent table?
Yes, nothing wrong with that. Just do it, it is correct.
While thinking about it: You might take a look at versioning of records. That is a step further but gives you even more info about who edited a record and when.