Add Ability to Search for Exact Answer Lines

[Lleytonio]

Add the ability to search for exact answer lines in database so I could search for things like violin without violincello results appearing.

[cmdun]

Add the ability to search for exact answer lines in database so I could search for things like violin without violincello results appearing.

I believe this can be solved by using the “search using regular expression” feature

[ani-per]

Add the ability to search for exact answer lines in database so I could search for things like violin without violincello results appearing.

I believe this can be solved by using the “search using regular expression” feature

You don't need regex for this case - using the "Search for exact phrase" flag will suffice for filtering out phrases that include the search phrase as a subset of the string.

[Lleytonio]

I think it would be easier if you had the ability to see only tossups with an exact answer line. The frequency list already tracks the number for each answer and I just want to see all of the tossups that are included in that number.

[ani-per]

I think it would be easier if you had the ability to see only tossups with an exact answer line. The frequency list already tracks the number for each answer and I just want to see all of the tossups that are included in that number.

I see. In that case, I think it would probably be pretty straightforward to add a dropdown and/or separate page that lists all the tossups without the user having to search for them manually on their own, since I imagine it would be a pretty simple query to generate the list in the backend.

@geoffrey-wu is that possible? If so, perhaps this issue could be renamed and pivoted towards that goal instead.

[geoffrey-wu]

I think the issue is being misunderstood - search for exact phrase won't filter out "violin player" for violin since it looks at word boundaries, and while regex can do this, not everyone has the ability to do this (e.g. you need to handle [] and () appearing in the answer)

that being said, I think the frequency list -> query idea is good, they can probably be made in conjunction

Also this is a duplicate of #447, I'll make this the main thread

[ani-per]

Ah I see, thanks! And sorry for the confusion that my answer might have caused, OP.