fen/uptime-kuma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

add back maxretries field

Browse source
This commit is contained in:
LouisLam 2021-07-30 00:13:48 +08:00
parent e6915d8964
commit f9a10d1672
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
db/patch4.sql
View file

@ -1,4 +1,6 @@
-- You should not modify if this have pushed to Github, unless it does serious wrong with the db. -- 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; PRAGMA foreign_keys=off;
BEGIN TRANSACTION; BEGIN TRANSACTION;
@ -20,11 +22,12 @@ create table monitor_dg_tmp
port INTEGER, port INTEGER,
created_date DATETIME, created_date DATETIME,
keyword VARCHAR(255), keyword VARCHAR(255),
maxretries INTEGER NOT NULL DEFAULT 0,
ignore_tls BOOLEAN default 0 not null, ignore_tls BOOLEAN default 0 not null,
upside_down 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; drop table monitor;