Cardinality (data modeling)

The cardinality of a join between two tables is the numerical relationship between rows of one table and rows in the other. Common cardinalities include one-to-one, one-to-many, and many-to-many.

For example, consider a database of electronic health records. Such a database could contain tables like the following:

  • A doctor table with information about physicians.
  • A patient table for medical subjects undergoing treatment.
  • An encounter table with an entry for each hospital visit.

Natural relationships exist between these entities, such as an encounter involving many doctors. There is a many-to-many relationship between records in doctor and records in patient because doctors have many patients and patients can see many doctors. There is a one-to-many relationship between records in patient and records in encounter because patients can have many encounters and each encounter involves only one patient.

A "one-to-one" relationship is mostly used to split a table in two in order to provide information concisely and make it more understandable. In the hospital example, such a relationship could be used to keep apart doctors' own unique professional information from administrative details.

In data modeling, collections of data elements are grouped into "data tables" which contain groups of data field names called "database attributes". Tables are linked by "key fields". A "primary key" assigns a field to its "special order table". For example, the "Doctor Last Name" field might be assigned as a primary key of the Doctor table with all people having same last name organized alphabetically according to the first three letters of their first name. A table can also have a foreign key which indicates that field is linked to the primary key of another table.

A complex data model can involve hundreds of related tables. Computer scientist Edgar F. Codd created a systematic method to decompose and organize relational databases. Codd's steps for organizing database tables and their keys is called database normalization, which avoids certain hidden database design errors (delete anomalies or update anomalies). In real life the process of database normalization ends up breaking tables into a larger number of smaller tables.

In the real world, data modeling is critical because as the data grows voluminous, tables linked by keys must be used to speed up programmed retrieval of data. If a data model is poorly crafted, even a computer applications system with just a million records will give the end-users unacceptable response time delays. For this reason, data modeling is a keystone in the skills needed by a modern software developer.

Database modeling techniques

The entity–relationship model proposes a technique that produces entity–relationship diagrams (ERDs), which can be employed to capture information about data model entity types, relationships and cardinality. A Crow's foot shows a one-to-many relationship. Alternatively a single line represents a one-to-one relationship.

Application program modeling approaches

In the object-oriented application programming paradigm, which is related to database structure design, UML class diagrams may be used for object modeling. In that case, object relationships are modeled using UML associations, and multiplicity is used on those associations to denote cardinality. Here are some examples:

RelationshipExampleLeftRight Narrative
One-to-oneperson ←→ birth certificate11 A person must have its own birth certificate
One-to-one (optional on one side)person ←→ driving license10..1 or ? A person may have a driving license
Many-to-oneperson ←→ birthplace1..* or +1 Many people can be born at the same place
Many-to-many (optional on both sides)person ←→ book0..* or *0..* or * A person may own books
One-to-manyorder ←→ line item11..* or + An order contains at least one item
Many-to-manycourse ←→ student1..* or +1..* or + Students follow various courses


gollark: It's some old system-rescue-CD thing.
gollark: Also, I have vital* data in the form of my Discord bot's database and website comments, and at least two people would be mildly irritated at the loss of those.
gollark: My journal is stored electronically, and I do somewhat want that, and it would be annoying if I lost my large media libraries.
gollark: I store a bunch of data on a ~10-year-old 7.2krpm HDD and the last backups are from August or so, fun™.
gollark: SSDs are still about 4x the price/GB.

See also

References
    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.