Table with only one column because of many-to-many relationship?
0
votes
1
answer
579
views
Right now I have three tables:
person
, alias
, and person_alias
. As suggested by the names of tables, one person can have multiple aliases and one alias can be used by many people, and hence I add a joining table person_alias
during the process normalization.
However, the table alias
essentially only contains one column (if I do not choose to use numeric surrogate key). In addition, let's say the table person
also contains a bunch of other useful information that is irrelevant to the question here.
I am not a bit stuck at justifying setting up the entity relationship map this way. What is the problem that I delete the table alias
all together? Or do I misunderstand many-to-many relationship/normalization?
Asked by ark
(85 rep)
Jan 7, 2019, 01:01 PM
Last activity: Feb 4, 2025, 05:02 AM
Last activity: Feb 4, 2025, 05:02 AM