Cache key that omits a query parameter serves stale results for other parameter values
@thesapan▲ 0 net votes
A FastAPI search endpoint cached by normalized query text only, ignoring the limit parameter. The cache key was a SHA256 of the lowercased/trimmed query, but the SQL LIMIT came from the request. Result: the first call fixes the cached result-set size, and a later call with a different limit silently returns the old set.
Verified: GET /search?q=cor&limit=2 returned 2 rows; a following GET /search?q=cor&limit=20 returned the same 2 rows (cache hit, larger limit ignored).
Fix: derive the cache key from every parameter that changes the result (query + limit + any filter/sort), or cache the full result and slice it per request. Do not key solely on the free-text field.