Search Results for "keys"

Nonblonde is a key/value database. Nonblonde tables are backed by b-trees that organize their nodes as critical bit trees. It allows multiple tables per store, atomic updates, keys of unlimited size. Head and tail key compression and a variable block size reduce the database disk size. Disk blocks are never modified in place, for which the written database is always in an intended state and does not need repair or recovery.

Levin is an event-based key/value server based on radix-tree (space optimized trie). Key search can be performed with an approximate key matching algorithm based on Levenshtein edit distance.

...It has both a C and a Python interface and is ACID compliant. Internally it uses an immutable B+ Tree. (Being append only doesn't mean that you can't replace records or delete keys).

NUB is a set of high class C++ codes providing indexes for variable-length keys, compressed resource files, and an istream interface for blocks of memory. Now supports Unicode keys and up to 17 trillion gigabyte file sizes. See www.cnub.org/NUB.ashx

PyTablet is a self organizing DB for semi-structured data. PyTablet behave like a huge persistable dictionary where keys are ID and values are dictionary-like objects that can link each other and contain simple values.

Does for a database what CVS does for code. Checkout a local copy of the db—current or back in time. Commit changes, pull updates, sync schema. Auto re-assigns & propagates conflicting keys. Atomic commits & row-level user rights + history tracking.

A unique flat-file database module, written in pure perl. True multi-level hash/array support, hybrid OO / tie() interface, cross-platform FTPable files, and quite fast. Can handle millions of keys/elements without significant slowdown.

[RETIRED] Tornado/DB is an object-relational mapping engine for Java. Features include object caching, multi-table inheritance, compound keys, relationships, XML config., JSP tags, small footprint.

Tiger is an object-oriented database, written in java. It uses the concept of primary keys, aggregates, relations and indexes for finding java objects in persistent storage. Tiger have support for transactions and remote access.

Java Object DBMS stores serialized java objects in a file with keys. The keys are automatically maintained. Heavy use of introspection minimizes programming burden. Future plans include transactions, network (RMI, SOAP) access.