19:I[99534,["52480","static/chunks/3b42e7c7-71ca6322932567b6.js","84665","static/chunks/ba8e36a0-38535765d282afbc.js","8447","static/chunks/75146d7d-ddf1b3135d4a2755.js","34726","static/chunks/8777d6a5-1dc02f220a7d6c64.js","21489","static/chunks/21489-03babd041db30949.js","44038","static/chunks/44038-fd3030a6e87c6658.js","56609","static/chunks/56609-8c93c3ffd3502a05.js","86848","static/chunks/86848-924d1d1b1ae426b7.js","14625","static/chunks/14625-b6bc097bca6b1160.js","24516","static/chunks/24516-09ab5354a4361405.js","42565","static/chunks/42565-26226f88189145be.js","4187","static/chunks/4187-902d61b1d079c69a.js","96457","static/chunks/96457-0142582a18c83b7d.js","90184","static/chunks/90184-af1effd41eb4ba67.js","18501","static/chunks/18501-427aa76b5a3fc40c.js","13918","static/chunks/13918-cc41d57e0fcd619b.js","57579","static/chunks/57579-098d1a47c94577aa.js","63250","static/chunks/63250-77464141783511fc.js","55519","static/chunks/55519-2ecba09026460f84.js","55439","static/chunks/55439-9e2859f9235b3146.js","31529","static/chunks/31529-45bc7e823ad9b319.js","4541","static/chunks/4541-9713285caa76c3f5.js","34008","static/chunks/34008-0c84560aef007e40.js","59594","static/chunks/59594-90f9c41358d8b442.js","14036","static/chunks/14036-6da36ce898253c2f.js","59266","static/chunks/59266-5498726bcbd0d76d.js","43652","static/chunks/43652-9dcfb13d521b4b2a.js","3368","static/chunks/3368-b35ab46e482c0fc4.js","33233","static/chunks/33233-f4787939ab1b0c30.js","72504","static/chunks/72504-f2d33587f048410c.js","29744","static/chunks/29744-cb31eac78da9e9b0.js","61786","static/chunks/61786-0473c121c37f59db.js","15674","static/chunks/15674-b43191f6fdf848a3.js","70599","static/chunks/70599-706de56c82899b1d.js","37198","static/chunks/37198-aaa9921f563b57cb.js","18255","static/chunks/18255-5a221c9e628b9753.js","22250","static/chunks/app/(free)/%5Bcategory-slug%5D/%5Barticle-slug%5D/page-7d1ca529ddf25f48.js"],"default"] 1b:I[92680,[],"IconMark"] 1a:Ta07,

As we discussed before, the number of times an entity of an entity set participates in a relationship set is known as cardinality. Continuing the discussion on cardinality, we explain Many-to-One cardinality relationships in this article.

Many-to-One (N:1) relationships in a database management system (DBMS) represent a scenario where multiple instances of one entity can be associated with one instance of another entity, i.e., multiple records in one table can be associated with a single record in another table.

Let's understand this with the example of an organization, say Zomato. Now Zomato has various departments for performing different operations in their company. One employee at Zomato can be part of only one department at a time, and as it is understood, several employees are part of one department.

Implementation:

In a Many-to-One relationship, the primary key is always on the "many" side. Thus, in the employee-department example, the Employee_id serves as the primary key, uniquely identifying each employee. The department each employee belongs to can be represented by a foreign key in the employee table.

Instead of creating three tables (two entity base tables and one relationship table), a Many-to-One relationship can be efficiently managed with just two tables:

Employee Table: Contains employee details and a foreign key indicating the department.
Department Table: Contains department details.

As a rule of thumb, in case of creating a relationship referencing table, the Primary Key is always created on the Many side of the relationship. Like in the above example, the Primary Key would be Employee_id since it would serve the purpose of a unique key for identification.

Though, in the case of Many-1 relationships, it isn’t necessary to have two entity