anchor.diff:  Another way to restate the last query we executed could be:
   
   ----
  -> jfdb:search(DB, {but, [[time], [place, p2]]}).
  +> jfdb:search(DB, {but, [time, [place, p2]]}).
   [{<<"k2">>,v2},{<<"k1">>,v1}]
   ----
   
  
positive.code: [{<<"k2">>,v2},{<<"k1">>,v1}]
  ----
  
  Notice how when searching, the return items are not always in order.
  If you are searching for a single index key, the order is guaranteed.
  All bets are off when performing complex queries over multiple keys.
  
  
negative.code: time test/jfdb test-db
  ----
  
  That test uses the `C` API to write just over 10,000 values.
  On my MacBook Pro I get *~30-40K* writes per second.
  
  Using the `Erlang` API:
  
  