h1. cl-bplustree - A Common Lisp implementation of an in-memory B+ tree.
*cl-bplustree* is an implementation of a in-memory B+ tree data structure in Common Lisp.
B+ trees main characteristics:
* All the data is in the leaves, internal nodes hold only keys used for traversal, pointers between the leaves are kept, so range-retrieval is easy and efficient.
* It is a generalization of a binary tree but instead of having only two pointers per node to other nodes it can have many more (this is called the order of the tree) because of this characteristic the tree has typically a large fanout and a small depth.
For more information about B+ trees, check "Wikipedia":http://en.wikipedia.org/wiki/B%2B_tree.
h3. @(bplustree-new (order &key key comparer))@
Creates a new empty B+ tre of the given order and returns it.
The _key_ parameter expects a function used to grab the key values (used for sorting) on whatever you are stuffing into the tree, the function will be called with one parameter (a record to be inserted into the tree for example) and it should return the value that will be used as a key. It defaults to @#'identity@.
The _comparer_ parameter expects a function used when comparing keys against each other in the tree operations. This function has to take two parameters (keys of records) and return a value depending on the following conditions:
@(< a b)@ -> -1
@(= a b)@ -> 0
@(> a b)@ -> 1
The meaning of this of course is given by your particular keys and your particular applications, for string keys for example @string<@, @string>@, etc., could be used.
This parameter defaults to a function that implements the explained logic but for numerical keys. If your keys are numeric, you don't need to supply a comparison function.
bc. (defparameter *my-tree* (bplustree-new 4 :key (lambda (r) (parse-integer r))))
h3. @(bplustree-insert (record tree))@
Inserts the given _record_ into the given _tree_, if the given key already exists in the tree, the value is updated. Returns the tree but is not needed to capture it and assign it,this call is not destructive on the tree itself, althought its internal elements are changed by it.
bc. (bplustree-insert "100" *my-tree*)
h3. @(bplustree-insert-many (tree &rest items))@
Inserts all the records given into the _tree_. Returns the tree.
bc. (bplustree-insert-many *my-tree* "5" "10" "-1" "1337" "212" "32" "311" "52")
h3. @(bplustree-search (key tree))@
Searches the value stored in the given _key_ in the given _tree_.
bc. (bplustree-search 311 *my-tree*) -> "311"
h3. @(bplustree-search-range (from to tree))@
Searches the tree for all the records that exists between the given _from_ and _to_ keys and returns them in a list.
bc. (bplustree-search-range 0 1000 *my-tree*) -> ("5" "10" "32" "52" "100" "212" "311")
h3. @(bplustree-delete (key tree))@
Deletes the record stored in the given _key_ in the _tree_. Returns the tree but is not needed to capture it and assign it, this call is not destructive on the tree itself, althought its internal elements are changed by it.
bc. (bplustree-delete 32 *my-tree*)
(bplustree-search-range 0 1000 *my-tree*)
("5" "10" "52" "100" "212" "311")
h3. @(bplustree-traverse (tree fn))@
Traverses all records in the tree in order from smallest to largest. As the B+ trees store data sorted already this operation is not expensive.
bc. (bplustree-traverse *my-tree* 'print)
h2. Final remarks
I hope this code is useful to you in any sense, either for learning, reading or maybe actual practical use, I will be very glad if you can even modify it to suit your needs. If you have suggestions please send them my way. Be sure to read *COPYING* file as well.