Content deleted Content added
Changed the header to be more descriptive of the content |
m Changing hyphen to en dash. |
||
Line 126:
The use of 1NF also comes with certain drawbacks:
* Performance worsens for certain operations. In a hierarchical model, nested records are physically stored after the parent record, which means a whole subtree can be retrieved in a single read operation. In 1NF, this will require a join operation per record type, which can be costly, especially for complex trees. For this reason, [[document-oriented database]]s eschew 1NF.
* [[Object-oriented language]]s represent runtime state as trees or [[directed graph]]s of objects connected by [[Pointer (computer programming)|pointers]] or references. This does not map cleanly to a 1NF relational database, creating a gap sometimes called the [[
* 1NF has been interpreted as not allowing complex data types for values. This is open to interpretation though, and [[Christopher J. Date]] has argued that values can be arbitrarily complex objects.{{citation-needed|date=June 2023}}
| |||