Liberalize res_code constraint
authorLebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Wed, 8 Aug 2012 15:56:54 +0000 (11:56 -0400)
committerLebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Wed, 8 Aug 2012 15:56:54 +0000 (11:56 -0400)
Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Open-ILS/src/sql/Pg/upgrade/XXXX.schema.url_verify.sql

index 1059cf2..5c8a9ab 100644 (file)
@@ -65,7 +65,7 @@ CREATE TABLE url_verify.url_verification (
     attempt     INT                         NOT NULL REFERENCES url_verify.verification_attempt (id) DEFERRABLE INITIALLY DEFERRED,
     req_time    TIMESTAMP WITH TIME ZONE    NOT NULL DEFAULT NOW(),
     res_time    TIMESTAMP WITH TIME ZONE, 
-    res_code    INT                         CHECK (res_code BETWEEN 100 AND 599),
+    res_code    INT                         CHECK (res_code BETWEEN 100 AND 999), -- we know > 599 will never be valid HTTP code, but we use 9XX for other stuff
     res_text    TEXT, 
     redirect_to INT                         REFERENCES url_verify.url (id) DEFERRABLE INITIALLY DEFERRED -- if redirected
 );