Behavior on join of namesake attributes does not match documentation

The currently implemented rule is that all the namesake attributes must be be part of the primary key in either of the operands. The documented and intended behavior is:
```All common attributes in both operands (attributes with the same name) must be part of either the primary key or a foreign key.```