Used ALTER TABLE instead of rebuilding the table

pull/238/head
Ponkhy 3 years ago
parent d313a06d5c
commit 02a12e68b8

@ -1,80 +1,10 @@
-- 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.
PRAGMA foreign_keys = off;
BEGIN TRANSACTION; BEGIN TRANSACTION;
create table monitor_dg_tmp ( ALTER TABLE monitor
id INTEGER not null primary key autoincrement, ADD dns_resolve_type VARCHAR(5);
name VARCHAR(150),
active BOOLEAN default 1 not null,
user_id INTEGER references user on update cascade on delete
set
null,
interval INTEGER default 20 not null,
url TEXT,
type VARCHAR(20),
weight INTEGER default 2000,
hostname VARCHAR(255),
port INTEGER,
created_date DATETIME default (DATETIME('now')) not null,
keyword VARCHAR(255),
maxretries INTEGER NOT NULL DEFAULT 0,
ignore_tls BOOLEAN default 0 not null,
upside_down BOOLEAN default 0 not null,
maxredirects INTEGER default 10 not null,
accepted_statuscodes_json TEXT default '["200-299"]' not null,
dns_resolve_type VARCHAR(5),
dns_resolve_server VARCHAR(255)
);
insert into
monitor_dg_tmp(
id,
name,
active,
user_id,
interval,
url,
type,
weight,
hostname,
port,
created_date,
keyword,
maxretries,
ignore_tls,
upside_down,
maxredirects,
accepted_statuscodes_json
)
select
id,
name,
active,
user_id,
interval,
url,
type,
weight,
hostname,
port,
created_date,
keyword,
maxretries,
ignore_tls,
upside_down,
maxredirects,
accepted_statuscodes_json
from
monitor;
drop table monitor;
alter table ALTER TABLE monitor
monitor_dg_tmp rename to monitor; ADD dns_resolve_server VARCHAR(255);
create index user_id on monitor (user_id);
COMMIT; COMMIT;
PRAGMA foreign_keys = on;

Loading…
Cancel
Save