CacheIncomingFile saves data from a given reader to a file.

NewDatabase initiates a new database object and binds it to a given directory.

NewDataset creates a new empty dataset.

NewRowReader creates a new RowReader based on loadSettings passed in - e.g.

OPTIM: pass in a bytes buffer to reuse it?.

ARCH: test this instead the Unmarshal? Or both?.

object types are reflected in the UID - the first two hex characters define this object type, so it's clear what sort of object you're dealing with based on its prefix.

object types are reflected in the UID - the first two hex characters define this object type, so it's clear what sort of object you're dealing with based on its prefix.

object types are reflected in the UID - the first two hex characters define this object type, so it's clear what sort of object you're dealing with based on its prefix.

object types are reflected in the UID - the first two hex characters define this object type, so it's clear what sort of object you're dealing with based on its prefix.

Config sets some high level properties for a new Database.

Database is the main struct that contains it all - notably the datasets' metadata and the webserver Having the webserver here makes it convenient for testing - we can spawn new servers at a moment's notice.

Dataset contains metadata for a given dataset, which at this point means a table.

Stripe only contains metadata about a given stripe, it has to be loaded separately to obtain actual data.

UID is a unique ID for a given object, it's NOT a uuid.

ObjectType denotes what type an object is (or its ID) - dataset, stripe etc.