#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.

  • Guest
  • Sep 5 2018
  • No Plans to Implement
  • Attach files
  • Guest commented
    10 Sep 08:45am
    Of course there would be a performance impact, as with many other design decisions, but this should be for the developer to consider when choosing to implement it.
  • Guest commented
    9 Sep 08:15pm

    Such an operation would come with limits or building/updating views would be much too costly. As venues go, (Notes)QueryResultsProcessor is a potential to deliver this. Actions like double clicking to open or Properties display would need design and careful thought but it's not infeasible.

  • Admin
    Thomas Hampel commented
    10 Jan, 2020 08:39pm

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

  • Guest commented
    7 Sep, 2018 01:35pm

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

  • Guest commented
    6 Sep, 2018 03:28pm

    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

  • Guest commented
    6 Sep, 2018 02:33pm

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

  • Guest commented
    6 Sep, 2018 07:59am

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

  • Guest commented
    5 Sep, 2018 06:29pm

    This is very vague. So please elaborate.

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