5,705
edits
Changes
Jump to navigation
Jump to search
Line 101:
Line 101: − − === Datastore features that could benefit Library === − These features can benefit [[Activities/Library]] activity. At present(for 0.82/0.84) Library uses "rich" datastore client which fetches all Journal objects to make short list of objects(by collapsing all versions to one item), moreover it has to unzip .xo bundles to get ''bundle_id'' value. So its not good. − − 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>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 − * ''bundle_id'' for .xo bundles in the Journal − * ''uid'' for other objecets − − <strong>Sort find()'s resultset</strong> − − Let datastore clients sort objects by any field(not only predefined like uid, activity_id etc). − * Sort by buddies count</strong> − − * Owner/Coordinator: ?
→Datastore features that could benefit Library: partly should be implemented in Version_support_for_datastore/Proposal, partly already implemented(sorting)
See [[Version_support_for_datastore/Proposal]].
See [[Version_support_for_datastore/Proposal]].
* Owner/Coordinator: Silbe
* Owner/Coordinator: Silbe
=== Security ===
=== Security ===