0
I am creating an Entity-Relationship Model in which a Student can have many Students, thus characterizing many to many’s self-relationship.
However, I am doubtful how to implement this relationship at the time of the bank’s creation. I must create the Student table and a second table possessing two Student keys?
If it helps, I’m doing this relationship to identify which friends a Student has added within the system.
Does that also apply to relationships? I am aware that indeed M-N cardinality relationships generate a third table, but in the case of an entity only relating to itself I cannot visualize the existence of three tables.
– Lucas Dirani
I get it. I think I misunderstood your problem. In this case you can simply put a key pointing to it yourself. It’s okay to do that. Using a lot to create categories that have subcategories or when they want to create the structure of a menu with submenus in the database.
– Vandemberg Lima