Matthew McGowan:
You would not see a difference in WU consumption since the filters are performed client side, they would not be part of WU consumption, however, if the search results are returned unfiltered from the server, based on the fact Bubble charges a small amount per character of data retrieved, there should be a difference in WU given a large enough dataset.
Yep, that’s what I meant.
Petter knows about it for sure:
Hey @greg18 ,
Thanks for posting! The difference that you bring up about :filters being performed server-side/client-side was one of the major revisions of the second edition of the book, and if that’s the version you’re referring to it may not be clear enough still (I can’t check the book right now, but thanks for including page numbers).
In the first edition, filters were described as being performed client-side more or less without exception, but it should have been made clear that this wil…
If you have the book - you can check these sections (I’m referring the latests 3rd edition):
Client-side vs server-side operators
How the :filtered (and other) operators works
Matthew McGowan:
The above from the manual is in a section specific to advanced filters and not the :filtered operator generally, which is why it states that those performed via the :filtered operator are generally “advanced” filters since most users would not use the :filtered operator for purposes other than advanced filters since most every other type of filter can be done via the ‘do a search’ constraints.
But still that’s confusing even for experienced Bubblers. I’ve pointed this to Bubble support and they’ve promised to look into it. May be @petter can update it
