@Teodor
I’m REALLY confused by something.
In MY case, I have a small dataset. 1000 recs. Basic registration info (name/addr/etc.) PLUS a few fields to filter by (f1, f2, f3)
I read the 2018 docs, Filtering Database Query with a Text Input. That modifies the QUERY to include the search text. I did this and it worked fine. And I believe its hitting the db each time you type a letter.
THEN I read your answer above and you said “This way your page won’t be reloaded when the url param value changes” because earlier you said “With Wappler you can filter your data on the fly”. In this post, you didn’t mention anywhere about modifying the QUERY to filter at the db., so I’m assuming the framework is filtering this on the client.
Whats hard for me to know is what best practice for today?
Maybe in 2018 you didn’t do this filtering you speak of in 2020?
Maybe now in 2022 something else has changed.
Since I have a relatively small dataset, I’m wondering if its not a bad thing to do the filtering in the client as @ellisdav was writing about, so I tried this with the “anchor buttons” and couldn’t make it work.
It appears for either of your methods that I DO NOT need to modify the Query (cause I’d want all records) and local filtering is occurring.
I’m back to trying “If an URL param is not needed” and I get all data from the query, but nothing happens when I click any of my buttons (the variable gets set, but the data doesn’t change).
And the bad thing is that I really want to user some Anchor buttons AND the search-text field, and have no clue which way to go.
I’m just trying to QUICKLY learn to get some results but I can’t seem to find the correct docs and as you see I’m questioning if what I’m reading is still valid. (example: I don’t even see an “App Connect”, only Server Connect.)
It seems really hard for a new user to grasp this tool because of outdated docs and renamed functionality.