5,705
edits
Changes
Jump to navigation
Jump to search
Line 271:
Line 271: − + − Let user call datastore.find() to get list of collapsed objects(all versions by one item). − That should mean that any datastore object should have "object id":+ − + − + − + − Let datastore clients browse history of collapsed objects: − * for ''activity_id'' objects - sort by timestamp (already impelemented) − * for ''bundle_id'' objects - sort by ''activity_version''(or so) field − <strong>Sort find()'s resultset</strong>
→Datastore features that could benefit Library
With all these features implemented Library can use "thin" datastore client and not fetch all objects, just make proper request for datasotre.find() to get sorted and collapsed objects by portions (by using offset/limit find() arguments).
With all these features implemented Library can use "thin" datastore client and not fetch all objects, just make proper request for datasotre.find() to get sorted and collapsed objects by portions (by using offset/limit find() arguments).
<strong>Get collapsed find()'s resultset</strong>
<strong>find() returns only last versions of journal objects</strong>
So, all objects should be grouped by "object_id" which could be:
* ''activity_id'' for objects that were generated by activities (already implemented)
* ''activity_id'' for objects that were generated by activities
* ''bundle_id'' for .xo bundles in the Journal
* ''bundle_id'' for .xo bundles in the Journal
* ''uid'' for other objecets (already implemented)
* ''uid'' for other objecets
<strong>History of collapsed object</strong>
<strong>Sort find()'s resultset</strong>
Let datastore clients sort objects by any field(not only predefined like uid, activity_id etc).
Let datastore clients sort objects by any field(not only predefined like uid, activity_id etc).
* Sort by buddies count</strong>
* Sort by buddies count</strong>