Premier League Predictor: FastAPI & PostgreSQL — Chapter 1, Exercise 1
====================================================

TASK
Explain the real difference between a "correct score" and a "correct
result" prediction, and describe one real scenario where a prediction
is a correct result but not a correct score.

SOLUTION

A "correct score" prediction means the exact scoreline predicted matches
the exact scoreline that actually happened — predict 2-1, the match
finishes 2-1, that's a correct score. A "correct result" prediction is a
looser, weaker win: the predicted win/draw/loss OUTCOME matches, even if
the exact numbers don't. Predict 2-1 (a home win) and the match actually
finishes 3-0 (also a home win), that's a correct result but not a
correct score — the direction of the outcome was right, the detail
wasn't.

Every correct score is automatically a correct result too, since getting
the exact scoreline right necessarily gets the win/draw/loss outcome
right as well. The reverse isn't true — a correct result can happen
without a correct score, which is exactly why these are two separate
things this app tracks per prediction, not one combined pass/fail flag.

A concrete example: the BBC's expert predicts Arsenal 1-0 Chelsea. The
real match finishes Arsenal 3-1 Chelsea. The scoreline is wrong (1-0
predicted vs. 3-1 actual — not a correct score), but the outcome is
right (a home win predicted, a home win happened — a correct result).

WHY THIS WORKS AS AN ANSWER
----------------------------
It states the two definitions precisely (exact scoreline vs. matching
win/draw/loss outcome), explains the real logical relationship between
them (correct score implies correct result, not the other way around),
and gives one concrete worked example with real numbers rather than
just restating the definitions abstractly.