GroundDB is a thin layer providing Meteor offline database and methods
This feature enables features recently added to the ground:dictionary and ground:minimax.
The dictionary is upgraded to allow the Date object as values. Now why is that important?
So Ground db rely on Minimax to compress the data, allowing more data in local storage. The Date fix allows Minimax to scan progressively meaning it now also adds values to the keyword dictionary.
Minimax was added a feature to have an initial dictionary, this will not be stored by Minimax since this is constant, by default false, true, null, undefined is added. Ground db adds _id, createdAt, createdBy, updatedAt, updatedBy to the database dictionary.
Looking at typical data much of the data is repeated like dates, ids and so on - for typical data the progressive mode will compress date better than before.
The ground db it self has improved in some areas like method resume - this is now much more fine-grained pr. connection. And the ground:stubfence solves some issues where data got added on reloads - because the method stubs ran again and could mutate data.
Scope has changed! The old GroundDB is now Ground.Collection
The grounddb object is now placed as an object on the collection instance.
The returned collection is an event emitter making event hook integrations much easier - events are changed, sync, cache, cached, method, methodcall, flush, error, resume, resumed.
The ground:test package is also supported now - The enables the automated qa test to integrate and give more detailed debugging details. Running ground db to run in a multi client / server test environment allows for some more complex scenarios - making the released versions less likely to break.