Terminology for Specific Kind of One-to-Many Relationship

All we need is an easy explanation of the problem, so here it is.

This question regards how a one-to-many row might "belong" to a different row and what exactly to call it. I might be asking for a term that does not exist.

Please see the below two tables. Customer and Address form a one-to-many relationship where one Customer might have many addresses. These Addresses "belong" to a Customer.


Now notice this table:


A single TaxCode could exist for many Addresses (a one-to-many relationship). But as I see it, Address doesn’t "belong" to TaxCode as Address "belongs" to the Customer. Address is a sort of "child" of Customer whereas Address just has a "link" to TaxCode. I don’t think the database "cares" since I think all the database rules are the same (e.g., foreign keys). But I’m wondering if specific names exist for these relationships beyond a one-to-many relationship.

In summary, I would like to know what to call the Customer-Address one-to-many relationship vs. the TaxCode-Address one-to-many relationship. Thank you.

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

I was looking for the terms identifying and non-identifying relationships. (This comment was posted by ypercubeᵀᴹ, so the thanks go to him.)

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply