Remove Challenge.LockCol

This database column (and corresponding model field) is not used by any Boulder logic.
letsencrypt · Feb 12, 2021 · 8866bca · 8866bca
1 parent f13b8db
commit 8866bca
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/sa/_db-next/migrations/20210211174900_DropChallengesLockCol.sql b/sa/_db-next/migrations/20210211174900_DropChallengesLockCol.sql
@@ -0,0 +1,10 @@
+
+-- +goose Up
+-- SQL in section 'Up' is executed when this migration is applied
+
+ALTER TABLE `challenges` DROP COLUMN `LockCol`;
+
+-- +goose Down
+-- SQL section 'Down' is executed when this migration is rolled back
+
+ALTER TABLE `challenges` ADD COLUMN `LockCol` BIGINT(20) DEFAULT 0;
diff --git a/sa/model.go b/sa/model.go
@@ -182,8 +182,6 @@ type challModel struct {
 
 	// TODO(#1818): Remove, this field is unused, but is kept temporarily to avoid a database migration.
 	Validated bool `db:"validated"`
-
-	LockCol int64
 }
 
 // newReg creates a reg model object from a core.Registration