From f9a10d1672af8a9c7d315eb0b08e1c5d730e70d0 Mon Sep 17 00:00:00 2001 From: LouisLam Date: Fri, 30 Jul 2021 00:13:48 +0800 Subject: [PATCH] add back maxretries field --- db/patch4.sql | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/db/patch4.sql b/db/patch4.sql index 66f93596..ff40da2e 100644 --- a/db/patch4.sql +++ b/db/patch4.sql @@ -1,4 +1,6 @@ -- You should not modify if this have pushed to Github, unless it does serious wrong with the db. +-- OK.... serious wrong, missing maxretries column +-- Developers should patch it manually if you have missing the maxretries column PRAGMA foreign_keys=off; BEGIN TRANSACTION; @@ -20,11 +22,12 @@ create table monitor_dg_tmp port INTEGER, created_date DATETIME, keyword VARCHAR(255), + maxretries INTEGER NOT NULL DEFAULT 0, ignore_tls BOOLEAN default 0 not null, upside_down BOOLEAN default 0 not null ); -insert into monitor_dg_tmp(id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword) select id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword from monitor; +insert into monitor_dg_tmp(id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword, maxretries) select id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword, maxretries from monitor; drop table monitor;