[go: nahoru, domu]

Key–value database: Difference between revisions

Content deleted Content added
Un1Gfn (talk | contribs)
→‎Types and notable examples: Berkeley DB is persistent (Disk=yes)
Un1Gfn (talk | contribs)
→‎Types and notable examples: link sdbm gdbm to section "DBM_(computing)#Implementations", instead of relying on redirects
Line 16:
Every entity (record) is a set of key–value pairs. A key has multiple components, specified as an ordered list. The major key identifies the record and consists of the leading components of the key. The subsequent components are called minor keys. This organization is similar to a directory path specification in a file system (e.g., /Major/minor1/minor2/). The “value” part of the key–value pair is simply an uninterpreted string of bytes of arbitrary length.<ref>[http://www.thinkmind.org/download.php?articleid=immm_2012_4_10_20050 Oracle NoSQL Database].</ref>
 
The Unix system provides [[DBM (computing)|dbm]] (database manager), which is a 1979 library originally written by [[Ken Thompson]]. It is also ported to [[Microsoft Windows]], provided through programming languages such as [[Perl#Windows|Perl for Win32]]. The dbm manages associative arrays of arbitrary data by use of a single key (a primary key). Modern implementations include [[BerkeleyDBM_(computing)#Implementations|sdbm, DB]]GNU dbm, [[sdbm]], and [[GNUBerkeley dbmDB]]. Although ''dbm'' precedes the concept of a NoSQL and is rarely mentioned in modern discourse, it is used by many pieces of software.
 
{| class="wikitable sortable mw-collapsible"