Jump to content

Talk:Cardinality (data modeling)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by SineBot (talk | contribs) at 21:02, 7 May 2010 (Signing comment by 84.147.211.226 - ""). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Stub‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.
Note icon
This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the |auto= parameter.

Can't a doctor have multiple patients and a patient multiple doctors? Wouldn't the example mentioned then be of a many-to-many and not many-to-one type?

Well it seems to be correct there: there is a many-to-many example regarding doctors and patients and one-to-many between doctors and departments. Zeratul021 (talk) 21:12, 15 January 2009 (UTC)[reply]

In this article the relational model is mixed up with ER-Modeling! There is no n:m relationship between relational tables. In ER modeling the cardinality of a relationship type is a constraint that limits the number of potentially related entities.

In the relationsal data model the cardinality of a table is the number of tuples (rows) in that table. —Preceding unsigned comment added by 84.147.211.226 (talk) 21:02, 7 May 2010 (UTC)[reply]