Alternative to “master” and “slave” in entity relationship?

Question

Example: I have two tables in my database called classA and classB, and one table called classA_classB. The last one just defi

Answer 1

there appear to be 3 competing industry alternatives to master/slave. they are:

• Master/Follower
• Parent/Child
• Primary/Secondary

I think primary/secondary is weird because we could have multiple secondary. I feel like after secondary would be tertiary, quaternary, etc. Too much of a pain.

Master/Follower still has vague slavery/feudalism connotations.

That leaves us just with Parent/Child... but I don't really like that because Child sounds incapable, but there are some cases where we'll depend on the Child, not the Parent....

SO, I'm going to suggest yet another combo here:

• Primary/Alternate

That naming should avoid any slavery, gender, and plurality issues.