At least to some bit. But aren't the filters completely in user-land code and I would be responsible for making sure what I am doing? I. e. checking if I have a child entity at hand? You guys cannot be responsible for every mistake your users make and limiting the functionality in one of the (already) few extension points makes things harder for the developer.
I understand that there might be cases when people implement a bad filter and things break down, but that can happen.
For us this thing is related to the security of our complete application and it makes a huge difference if a user must be allowed to view every entity of a inheritance hierarchy or I can define on a much more granular level. And for using a filter to limit the result returned from the DB is the logical place to do so.
I also would be happy to hear some kind of suggestion what I could do instead, not only a "will not fix, not my problem" kind of response
Are there any filters implemented in the main ORM project?