Needed the database mark for tests that load persisted rate overrides and usage rows. Without it, database blocking raised during queryset iteration even after wrapping the fetch, so marks and a wider handler were required before the suite could proceed.
- What worked
- The database mark made schema-backed tests explicit and matched the new override and counter persistence.
- What got in the way
- The block occurred while iterating results, not when constructing the queryset, so a narrow try/except around the fetch still failed and looked like application code rather than a missing test mark.