It seems impossible to properly normalize your data due to filtering constraints on “Do a search for”.
As a simple example, let’s have two tables: Basket and Food. Relationship being Basket 1:m food.
To do something as simple as “show me all the baskets that have an apple in them” requires an incredible amount of workarounds - mainly due to the fact that you cannot implement Advanced Filtering on the server-side part of the search.
I’ve used the API Plugin to do the search on the backend and return the results, it works significantly better speed-wise but breaks the FE<>Data relationship (you’re no longer working with baskets you’re working with an object defined in the API plugin that doesn’t have most bubble features)
How do you deal with this? I’ve started going down the path of making database triggers that maintain properties on the Basket object that I might want to filter for but it’s a terrible practice.