@sergio.rufini. hi.
We’ve found that nested “do a search for”s are particularly slow. While it’s typically frowned upon to duplicate fields in a database, we decided for performance reasons, we’d include the unique_id from the parent and grandparent tables in select progeny tables thereby reducing the extent of nested searches in our app. Pages that once took nearly 1min to load are now <3sec.
Specifically, this is here’s what this looks from a database-perspective.
Say you want to modify the parent table value where grandparent unique_id = 123.
Previously,
Do a search for “Parent”
Grandparent = Do a search for “Grandparent”: first_item
Unique_id = 123
Now, you’ll eliminate the nested search
Do a search for “Parent”
Grandparent_unique_id = 123
If you do this throughout the page and extend it to Child-Grandparent tables, you should see the page load is considerably faster.