If you can query on membership in web view but not database view it requires you to create a query in database view and bring it into webview in order to continue to filter by membership information.
We know it's difficult living in this dual world where there are some capabilities in the old database view that aren't accessible in the WebView yet. That being said, in order to expedite our transition over the WebView, we will not be retroactively adding new features from WebView back into the database view.
We have limited resources and that would mean that every feature we work on would take over twice as long as we would be building if in the new, quick WebView engineering world, and the slower, harder to engineer for, database view world.
We want to quickly build out new features and keep moving forward with our solution, and in order to protect that focus, we need to say no to adding more features to the database view.