normalized-db / data-store Goto Github PK

For the sake of component-independence, BaseCommand should not refer to any class depending on a certain persistence layer.

Move key from item-object to a separate argument

Replace Logger.clear(…), Logger.clearType(…) and Logger.clearItem(…) by a ClearLogsCommand-interface and context-sensitive implementations. See other commands (e.g. ClearCommand) for a reference.

Sort documents by an order-by-object declaring multiple fields with a sort-order. The order of the fields can be used as priority. The following would sort documents with a name and a date field (names in ascending order, dates in descending order but only in case names are not equal).

query.orderBy({
   name: Query.ORDER_ASC,
   date: Query.ORDER_DESC
});

null-/undefined-values could be ignored and skipped, so if one name is not set, the comparison would automatically continue with the dates. A boolean-flag could determine whether each field in the order-by-object is required or not.

Restriction: Only default types (string, number, Date) could be compared. Complex type would either require a user-defined callback or (better) nested fields. E.g. query.orderBy({ subDocument.title }); would check if the subDocument- and subDocument.title-fields are set and then sort by these sub-titles.

Check _refs for other documents referencing the object which should be removed during a cascaded removal

Add support for fetching partial documents (see Projections from MongoDB)

Add a subdocument to multiple parents at once