Ansgar, yep, it's custom query.
actually changing the query is not easier. often you have to work with tables with more than 50 columns. and you need to look at a specific column for a moment. and then return it as it was. it would be very convenient to find the required column through the filter, and return the full display back. this is 2 seconds * the number of hours of work with tables. savings hours per year. :)
I have not seen this feature in any GUI program for working with tables. Everyone filters only data, not columns.
It will be faster because no need to waste time on the network (while the request is sent, while it is processed, while it returns). because the filter will work with data that has already been received.
If you decide to implement this functionality, then here is my advice for which all data analysts will be grateful to you:
all table columns: id, dtsent, dtarrive, dtpaid, firstname, status, sum, service_id, metrica_id
filter data: "dt"
displayed columns: dtsent, dtarrive, dtpaid
filter data: "id"
displayed columns: id, dtpaid, service_id
filter data: "_id dt"
displayed columns: service_id, metrica_id, dtsent, dtarrive, dtpaid