I apologise if this has been asked and answered before but is the “Do search for” function considered bad or slow in terms of data sourcing or retrieval? I’m developing a complex (for me) app and every time I use “Do search for” (with the correct constraints) to pull results/data I always think this is a failing of my database structure. I find that when I have to use “Do search for” in a repeating group then the results aren’t loaded “instantly” and instead I may have to wait (0.5secs) before they’re loaded as apposed to instantly when querying specific data types.
I guess I’m worried that as more and more data is saved in to the DB and the more I rely on “Do search for” the slower and slower my app will take to retrieve data.
Is this correct or am I overthinking it? I’m assuming the more constrained my constraints are then I might be fine? Any advice would be greatly appreciated!
There is nothing wrong with using “Do a search for…” to return data, in fact this is the main way to search the database and return records.
Its use case will depend on the context of your app, but in general it will be widely used. In terms of performance and speed, everything will depend on your database structure, the weight of the data, amount of data returned, amount displayed in your Repeating Group, the use of pagination, search constraints, applied filters, privacy rules, etc.
There are several things that, when added together, can contribute to a good or bad experience, performance and speed.
the do a search isn’t slow, though the speed increases more by adding constraints
another way the page load may be slow is how you structure your database.
