yousefshokati wrote:
Hi And tanks for your answer
You're welcome :)
yousefshokati wrote:
You say that When we design our database , we should design in a way that we do not have any closed path ?
Am I right?
I'm saying that you should normalize the design; that will eliminate all weird stuff from the design and give you something you can work with. I know that it's a bit of an investment in terms of time, but it repays itself rather quickly.
yousefshokati wrote:
We have MembersTable Which represents the members of teams and we have TeamsTable That represents the Team Entity Now We have to relations between these 2 . The First relation is "Plays For" which means that "Member Plays for team A for example " and the second is "Captain Of" which stands for "Members x is captain of team A" . Now if we update one of these FK s that are in tables for creating the relationships then we will get an error , won't be?
Yes, you will. Normalization would state that you don't need the second entity. MembersTable MemberId MemberName IsCaptain Best wishes for the year to come :)
Bastard Programmer from Hell :suss: