Sometimes, it's not enough to know what the easy prey is. You also need to know whether you will be able to hunt it down. What good is an almost turned haskell zombie if you cannot read the functional incantations of the language? How will you as a vba guru handle a python behemoth?
That's why I present to you the tag-based zombie sniffer:
SELECT q.Id AS [Post Link], q.Tags FROM Posts q INNER JOIN Posts a ON q.Id = a.ParentId INNER JOIN PostTags ON q.Id = PostTags.PostId INNER JOIN Tags ON PostTags.TagId = Tags.id WHERE q.AnswerCount > 0 AND q.AcceptedAnswerId IS NULL AND Tags.TagName = '##TagName##' GROUP BY q.Id, q.Tags HAVING MAX(a.Score) >= ##MinScore:int?0## AND MAX(a.Score) <= ##MaxScore:int?0## -- TagName: Tag name "as you would use in your post" -- MinScore: Highest answer has at least votes: -- MaxScore: Highest answer has at most votes:
You can find it on SEDE.
As it's predecessor, it looks for easy prey by default:
- questions that have at least one answer
- no answer has a score of more than 0
- the highest scored answer has a score of at least 0
- has no accepted answer
However, this one also takes a tag name so that you can search for C++ zombies or similar. This is the first time I've ever written an SQL query with three
JOINs, so I have no idea whether this is considered good style. Also, I group by the
q.Tags to show them in the result, but I think that's a hack and not really good style.