Home/ Questions/Q 6122317
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T15:53:05+00:00

Take the following database tables |========| |user | |========| |id | |username| |password| |========|

  • 0

Take the following database tables

|========|
|user    |
|========|
|id      |
|username|
|password|
|========|

|=========|
|blog     |
|=========|
|id       |
|date     |
|content  |
|author_id|
|=========|

blog.author_id is supposed to connected to a particular user.id, whichever user who wrote the blog entry obviously.

My question is with regards to 1:1, 1:n identifying and non-identifying relationships… I don’t really understand them very much. Should this relationship be one of these types of relationships or not? And if so, which one? And what is the advantage of this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In this example, there’s a 1:1 relationship between a blog record and an author. The reason they exist as separate entities/tables is the grouping of information — user related stuff doesn’t belong with a blog record, and it could be duplicated if someone writes more than one blog.

    The reason you want that implemented as a foreign key constraint is because the constraint ensures that the author for the blog record exists in the user table. Otherwise, it could be nonsense/bad data. The foreign key doesn’t stop duplicates — you’d need a primary or unique key for that — the foreign key only validates data.

    Now that Nanne clarified the identifying/non-identifying terminology for me, the blog.author_id would be the identifying relationship. Because it’s identifying who (what user record) the author is.

    The id column in both tables can be assumed to be be the primary key, because an artificial/surrogate key is the most common primary key. Which makes these columns the non-identifying relationship…

    • 0