Loading problem...
A curriculum analytics team collects community reactions for each coding problem and wants to identify low-approval items that may require editorial revision.
Table: problem_feedback
Definition:
Task: Return the IDs of all low-approval problems.
Output requirements:
Supported submission environments:
problem_feedback:
| problem_id | likes | dislikes |
|------------|-------|----------|
| 6 | 1290 | 425 |
| 11 | 2677 | 8659 |
| 1 | 4446 | 2760 |
| 7 | 8569 | 6086 |
| 13 | 2050 | 4164 |
| 10 | 9002 | 7446 |[
{"problem_id":7},
{"problem_id":10},
{"problem_id":11},
{"problem_id":13}
]Problems 7, 10, 11, and 13 have approval rates below 60%. Problems 1 and 6 are at or above 60%, so they are excluded.
problem_feedback:
| problem_id | likes | dislikes |
|------------|-------|----------|
| 100 | 3 | 2 |
| 101 | 6 | 4 |
| 102 | 59 | 41 |
| 103 | 599 | 401 |[
{"problem_id":100},
{"problem_id":102},
{"problem_id":103}
]Problem 101 is exactly 60%, so it is not low-approval. The others are strictly below 60%.
problem_feedback:
| problem_id | likes | dislikes |
|------------|-------|----------|
| 201 | 0 | 0 |
| 202 | 0 | 9 |
| 203 | 8 | 0 |
| 204 | 6 | 4 |[
{"problem_id":202}
]Problem 201 has undefined approval rate (0 total votes), so it is ignored. Problem 203 is 100% and problem 204 is exactly 60%, so neither is returned.
Constraints