Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino Designer
Created by Guest
Created on Sep 18, 2019

Add dynamic sort options to domino-db module function bulkReadDocuments

Our endusers expect data returned by the Proton Node.js applications to be sorted. As a developer, I need to build scalable solutions that work with large datasets.

Currently the DQL search results returned by the domino-db module are not sorted. Sorting is up to the Node.js application which does not scale.

 

We need two options to let Domino sort the results:

  1. by a fieldname ASC/DESC
    The Proton task would search the database design to find a SELECT @All view that has a sorted view column containing the specified fieldname in the requested sort direction. The DQL results are returned in the order they appear in this column.
    If no such column exists, the lookup results in an error (=> the Node.js app has to manually create an index on the field).
  2. by a named view column ASC/DESC
    The Proton task would return the DQL results in the order they appear in a view column. 

 

Both sort options would support paging. So passing an start/count into the bulkReadDocuments methods would return a subset of the sorted data.

 

Karsten Lehmann, Mindoo GmbH

  • Attach files
  • Guest
    Reply
    |
    Jan 17, 2020

    In plan - John Curtis

  • Guest
    Reply
    |
    Sep 19, 2019

    For LS/Java they already added this feature in R10:

    ViewEntryCollection.intersect(DocumentCollection dc, boolean maintainOrder) with maintainOrder = true

     

    Should not be a real problem to do the same in the Proton task and use the already existing design catalog to find, resort and use the right view.

  • Guest
    Reply
    |
    Sep 19, 2019

    Agree. This is a must-have for DQL.

    By the way: I saw 'Sorted results' mentioned for 'beyond V11' in a presentation from HCL titled 'Domion App Dev'. Not sure if that includes paging.