Difference between revisions of "Attribute–value pair"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (→See also) |
Karl Jones (Talk | contribs) (→See also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 17: | Line 17: | ||
== See also == | == See also == | ||
| + | * [[Attribute (computing)]] | ||
* [[Data]] | * [[Data]] | ||
* [[Data (computing)]] | * [[Data (computing)]] | ||
* [[Data model]] | * [[Data model]] | ||
* [[Data structure]] | * [[Data structure]] | ||
| + | * [[Entity–attribute–value model]] | ||
| + | * [[Query string]] | ||
* [[Tuple]] | * [[Tuple]] | ||
| + | * [[WordPress Custom Field]] | ||
| + | |||
[[Category:Data structures]] | [[Category:Data structures]] | ||
Latest revision as of 17:39, 25 October 2016
A name–value pair, key–value pair, field–value pair, attribute–value pair, etc. is a fundamental data representation (see Data (computing)) in computing systems and applications.
Tuples
Designers often desire an open-ended data structure that allows for future extension without modifying existing code or data.
In such situations, all or part of the data model may be expressed as a collection of tuples, like this:
<attribute name, value>
Each element is an attribute–value pair.
Uniqueness of attribute names
Depending on the particular application and the implementation chosen by programmers, attribute names may or may not be unique.
See also
- Attribute (computing)
- Data
- Data (computing)
- Data model
- Data structure
- Entity–attribute–value model
- Query string
- Tuple
- WordPress Custom Field
Exterior Links
- Attribute-value pair @ Wikipedia
