Partly. The data in the database is not built for reporting at all, but it is completely re-organised in the index. The index is also not built for reporting, but it is built for searching and so the information like "number of results from a filter" is quickly available without having to run the filter against the database and count.
Exactly as Roberto says, the act of filtering has no effect on the data, it's completely read-only.
To "optimise" filters though, you just keep them as simple as possible.
The filter is always updated in real time. Whether saved or not, just redo the search.
What do you mean by optimizations?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The action of just filtering does not interfere with the items. You can do this in a second action, if you wish. But filters work like queries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, @Roberto Miasack
What do you mean by optimizations
Optimisations could be creating indexes based on the where clause of a saved filter. Looks like that is the case from @Nic Brough -Adaptavist- 's comment
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.