v0.0.5

• Bugfix: ordering by a part of an index would sort all matching records by the
  remaining orderings not handled by the index, undoing the ordering of the index.
• Use more of an index for orderings:
  • If we have an exact filter from an index that we also order on, recognize
    that as having fulfilled the ordering requirement.
  • Let more than 1 ordering be fulfilled with multi-key indices. only if they
    have the same direction.
  • Our index keys have one or more fields, followed (implicitly) by the value of
    the primary key. If we have consumed our index, and there is still an
    ordering to apply (of same direction) by primary key, also fulfill that
    primary key order through the index.

v0.0.4

- Fix exporting records of (fixed length) array types that have zero values.
  The export code didn't take the fieldmap (used to store only the nonzero
  values) weren't taken into account when exporting). This function is used by
  the bstore command when exporting to CSV or JSON. This is not used during
  regular database operation.

v0.0.3

- bugfix: Query.Delete and probably Query.Update* would not affect all records that match the query in certain data-dependent cases

v0.0.1

First tag. Plan is to keep the storage format compatible in the future. More
seemless schema updates may be allowed in the future. The API could still
change, but incompatible changes will not be made lightly.