first round of all_projects table generation. this is entirely hardcoded, so it ain't future proof. We need a way to do this programmatically.
parent
1106b38346
commit
14497754f5
@ -0,0 +1,29 @@
|
||||
DROP VIEW IF EXISTS all_projects;
|
||||
|
||||
CREATE TABLE all_projects AS SELECT * FROM CLT2019
|
||||
UNION
|
||||
SELECT * FROM CLT2020
|
||||
UNION
|
||||
SELECT * FROM CLT2021
|
||||
UNION
|
||||
SELECT * FROM CLT2022
|
||||
UNION
|
||||
SELECT * FROM RDU2019
|
||||
UNION
|
||||
SELECT * FROM RDU2020
|
||||
UNION
|
||||
SELECT * FROM RDU2021
|
||||
UNION
|
||||
SELECT * FROM RDU2022
|
||||
UNION
|
||||
SELECT * FROM ENV2020
|
||||
UNION
|
||||
SELECT * FROM ENV2021
|
||||
UNION
|
||||
SELECT * FROM ENV2022
|
||||
UNION
|
||||
SELECT * FROM SRV2020
|
||||
UNION
|
||||
SELECT * FROM SRV2021;
|
||||
|
||||
CREATE UNIQUE INDEX ref_num ON all_projects(refnum);
|
||||
Loading…
Reference in New Issue