#dominoforever | Product 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

@dblookup / @dbcolumn for views

To implement information from another view without saving it in the document.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 5 2018
  • Unlikely to implement
  • Attach files
  • Admin
    Thomas Hampel commented
    10 Jan 20:39

    Unlikely to do it exactly as proposed, but we're working on a different method that would allow what you're planning to do.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 07, 2018 13:35

    I t think driving need here is a Domino equivalent of JOINs.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 06, 2018 15:28

    Performance will surely depend on how its implemented and then used?

    If as you say 30k documents result in 30k lookups, and it was built so that clients actually do the lookup when reading the view, then yes I can imagine performance would be bad.


     - If 30k documents only result in 50 - 100 actual database lookups (IDs -> Values) and the results are cached in memory during the view index update then performance would be better

     - If the lookups are performed by the server as part of the view index update/rebuild processes and the values stored in the view index then clients can (hopefully) just read the view contents as quickly as they do now

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 06, 2018 14:33

    It soundss really performance intensive.  Imagine a 30k document view, doing 30k @DBLookups for one column just to load the view.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 06, 2018 07:59

    Yes, correct. Some information only need in the view for the user and not need to safe in the document.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 05, 2018 18:29

    This is very vague. So please elaborate.

    I assume you like to use @dbcolumn and @dblookup inside a column formula of a view?