purge settings data reset

Purging league data

What a purge deletes, what it deliberately keeps, and why it cannot be undone.


A purge is a hard delete and cannot be undone

Rows are removed from the database rather than flagged. A purge that left rows behind would let the next upload collide with records nobody can see.

It is scoped to the league you are signed in to by the same filter that scopes every other read, so it cannot reach another league’s data — but within this league there is nothing to undo it with.

What goes and what stays

Settings → Purge league data. The page shows live counts of exactly what would be deleted before you confirm. At Warrington that is currently 11,458 rows.

DeletedKept
Divisions, clubs, teams and team entriesThe league itself, and its subdomain
Fixtures, results and matchdaysSeasons
Ratings and rating historyAge groups, their formats and score visibility
Banding reviewsEach age group’s banding policy
Structure publicationsThe audit trail, including a record of the purge itself
Upload history

The split is deliberate: what is kept is configuration the league chose, not data the weekly file carries. Throwing it away would make every purge a re-onboarding.

Confirming

Confirmation is by typing the league’s full name — Warrington Junior Football League — into the box. The button then reads Purge N rows with the real count.

The usual reason to purge is starting again from week one: clear the slate, then upload the first full fixture export of the season.