Currently, when you “Do a Search For…” to grab data from your database in Bubble, it pulls every column for that row.
I’ve attached an example of a table I have - A Type for “Tickets”.
If I “Do A Search For…”, it pulls every single column of data for that one ticket (Approval-ID, Archive, description, etc. etc.).
By using the “Inspect” button in Preview mode, I find that even if I am simply looking to display a Ticket description, all columns of data are pulled… In this example, you can see Scope Association is also being pulled.
Would this be a potential performance gain?
When we do a “Do a Search For…” , allow us to select only the columns we wish to pull data from. In my example above, if I just wanted to pull Ticket Description, it wouldn’t pull the Scope Association and all of that baggage! (Another forum post talked about adding a Privacy rule, however I feel this would be straightforward).
For the programmers out there, this would be similar to how SQL allows a SELECT statement to choose columns versus a “*” to gather all columns (I know Bubble’s database is not SQL). A major performant gain for larger applications.
Giving us the power to reduce the amount of data we are bringing to our pages should bring an overall benefit to performance as a whole.
(Is it possible that this is already implemented and the “Inspect” button that I’m getting this information for is showing me all the data just to help with debugging?)