attempts

Table actions
PO (presentation order)
the order in which the contestant's prize, VT, work of art, or live attempt was presented; 0 for simultaneous (most live tasks)
± (adjustment)
any alteration (bonus or deduction) applied to the attempt's base score
episode
the contestant's cumulative episode score after this task
series
〃

5 rows where task = 442

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: series

id ▲ task contestant PO base ± points rank episode series team location
2120 The best thing that probably has a spring 442 Daisy May Cooper 53 5 1   1 5 1 30    
2121 The best thing that probably has a spring 442 Johnny Vegas 54 4 5   5 1 5 30    
2122 The best thing that probably has a spring 442 Katherine Parkinson 55 2 2   2 4 2 27    
2123 The best thing that probably has a spring 442 Mawaan Rizwan 56 3 4   4 2 4 28    
2124 The best thing that probably has a spring 442 Richard Herring 57 1 3   3 3 3 34    

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE attempts (
   id         INTEGER PRIMARY KEY,
   task       INTEGER REFERENCES tasks(id),
   contestant INTEGER REFERENCES people(id),
   PO         TEXT,
   base       INTEGER,
   adjustment INTEGER,
   points     INTEGER,
   rank       TEXT,
   episode    INTEGER,
   series     INTEGER,
   team       INTEGER REFERENCES teams(id),
   location   INTEGER REFERENCES special_locations(id)
);