@pirate Please review.

I'm worried that while this enables filters working, it will hide some results that only match via external backend search index but dont match via SQLite db field search (or vice-versa).

e.g. if user searches for some string that's only present in a tag, but not in the snapshot content

Maybe better to extract the filter parameters passed from the UI and apply them to the queryset manually?

Interesting. I thought the search results would contain that information. So when we do perform & operation the final set would have the results matching both. Let me go through the code and figure it out. Thanks.

I merged just the .distinct() fix for now, happy to review other PRs in the future for other changes, though lets discuss them in an issue first to make sure all the use cases are handled :)