Rework primary keys in the match list scouting database
We don't need a separate ID for the rows in the match list table. We
really just care about a unique combination of `MatchNumber`, `Round`,
and `CompLevel`.
This will make it easier to update an existing match list. We
currently don't support this.
Signed-off-by: Philipp Schrader <philipp.schrader@gmail.com>
Change-Id: I7d42dab7695cfee4844bbb7660ed820bb083b199
diff --git a/scouting/webserver/requests/requests_test.go b/scouting/webserver/requests/requests_test.go
index b864cf3..e2d9219 100644
--- a/scouting/webserver/requests/requests_test.go
+++ b/scouting/webserver/requests/requests_test.go
@@ -360,6 +360,7 @@
{
CompLevel: "qual",
MatchNumber: 1,
+ SetNumber: 2,
Alliances: scraping.Alliances{
Red: scraping.Alliance{
TeamKeys: []string{
@@ -411,7 +412,7 @@
expectedMatches := []db.Match{
{
MatchNumber: 1,
- Round: 1,
+ Round: 2,
CompLevel: "qual",
R1: 100,
R2: 200,