21 lines
1.0 KiB
MySQL
21 lines
1.0 KiB
MySQL
|
-- Remove planning and controls fields
|
||
|
|
|
||
|
|
--Landuse is hierachical. Highest level is Order (Residential) then Group (Residential-Dwelling) then Class (Residential-Dwelling-Detached house)
|
||
|
|
|
||
|
|
--Fields could be linked when not mixed use Example: If user inputs class field (Detached-House) on front end then trigger on db automatically will populate group and order. If we go this route then a trigger is needed on the db both to run and remove this process.
|
||
|
|
|
||
|
|
-- Land use, single or mutiple classes?
|
||
|
|
ALTER TABLE buildings DROP COLUMN IF EXISTS landuse_mutiple_use;
|
||
|
|
|
||
|
|
-- Land use, how many different uses?
|
||
|
|
ALTER TABLE buildings DROP COLUMN IF EXISTS landuse_number_of_uses;
|
||
|
|
|
||
|
|
-- Land use NLUD class, this might be multiple and should match number of uses input
|
||
|
|
ALTER TABLE buildings DROP COLUMN IF EXISTS landuse_class;
|
||
|
|
|
||
|
|
-- Land use NLUD group, can only be one - prepopulated if mixed
|
||
|
|
ALTER TABLE buildings DROP COLUMN IF EXISTS landuse_group;
|
||
|
|
|
||
|
|
-- Land use NLUD order, can only be one - prepopulated if mixed
|
||
|
|
ALTER TABLE buildings DROP COLUMN IF EXISTS landuse_order;
|