So, I pitched this idea (or so I thought):
“Let me search a table with 20 fields but only return 2 fields as results to save time and improve performance. Simple, right?”
But instead of saying, “Wow, great idea!” Bubble replied with, “You can use a search filter to choose which fields to return!”
Now, I’m sitting here wondering if they read my description or just skimmed it like it was the terms and conditions on a free app. Filters are great and all, but that’s not what I meant! I’m talking about limiting the actual fields retrieved, not filtering results after fetching all 20 fields.
So here’s the situation:
My idea: “Can I just get two fields back instead of the whole table?”
Bubble’s response: “Have you tried using filters?”
Me: facepalm
Do I need to write “Please read the full description” in bold next time? Help me out, folks—my idea deserves better!
The thing is, all that extra workload we face because of this limitation doesn’t just cost us time—it also ends up costing Bubble itself. Why? Because more data loading = more processing = more strain on Bubble’s servers = more $ for infrastructure.
Josh stated it was on their list…unfortunately, it seems to be something that tends to go on the list and then taken off and then put on again. I wouldn’t expect them to do this anytime soon, if every at this point since it has been more than 1.5 years since Josh said it was on the list.