When creating a relationship between two tables with columns that have already been created, building a relationship creates a new duplicate column in the child table instead of looking to see if a column with the same name as the referencing table.column already exists in the child table.
The logic behind this should be conditional:
1. Check to see if referencing column name exists in child table:
. 1a. If yes, use the already existing column for the relationship
1b. If no, create a new column
This is annoying and unintuitive for enterprise database design.
Customer support service by UserEcho