• DBTable en DBQuery have two different filters:


  1. Filter. Works on the master table
  2. SubFilter. Works on the cache table


Again, it is important to see the difference. The content of the cache table does not change when you alter the subfilter. So even if the data is in the main table, if it isn’t in the previous search result it will not be found (unless you refresh the query). Changing the filter will reopen the query.


  • Except the floating filters described above, PHsPeed also has a fixed filter.


The filter also plays an important role at master-detail relationship, but PHsPeed might alter the filter depending on the situation. But what if you want to work with a subset of data and want to maintain that filter? 

For instance you want to work on a table of employees that belong to a certain department. Other employees may not be selected. It is possible to realize that with a filter, but you have to be aware on each query that you have to apply this. 

In PHsPeed there is a fixed filter. No matter what, this filter will always be applied additionally to the search result. So if you set a filter, PHsPeed will append the fixed filter to it. That way you can be sure that users will only see employees that they are allowed to. PHsPeed never touches the fixed filter property.

This is a very convenient way and makes maintaining GDPR regulations more easily.