challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit b2e71e2a0e5cb4d11dc881cc057a3a0ac0221aab
parent 15434ec4cf3ba0c9f023eb974358bc70a2f20130
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu,  6 Aug 2026 15:17:10 +0200

drop redundant index

Diffstat:
Msrc/challengerdb/challenger-0005.sql | 8++++++++
1 file changed, 8 insertions(+), 0 deletions(-)

diff --git a/src/challengerdb/challenger-0005.sql b/src/challengerdb/challenger-0005.sql @@ -31,4 +31,12 @@ ALTER TABLE validations COMMENT ON COLUMN validations.pending_pin IS 'PIN that was passed to the AUTH_COMMAND helper but whose transmission was not confirmed yet; promoted to last_pin when the helper terminates successfully'; +-- challenger-0004 made validation_serial_id the primary key, but (unlike for +-- 'clients', where it dropped clients_client_serial_id_key) it left the +-- now redundant UNIQUE constraint from challenger-0001 in place. +ALTER TABLE validations + DROP CONSTRAINT IF EXISTS validations_validation_serial_id_key; + + + COMMIT;