Fix errors in landuse migrations
This commit is contained in:
parent
20e9299226
commit
76def0022f
@ -12,7 +12,7 @@ ALTER TABLE buildings DROP COLUMN IF EXISTS current_landuse_class;
|
|||||||
ALTER TABLE buildings DROP COLUMN IF EXISTS current_landuse_order;
|
ALTER TABLE buildings DROP COLUMN IF EXISTS current_landuse_order;
|
||||||
|
|
||||||
--Land use class, group and order will be stored in a new table
|
--Land use class, group and order will be stored in a new table
|
||||||
DROP TABLE building_landuse IF EXISTS CASCADE;
|
DROP TABLE IF EXISTS building_landuse CASCADE;
|
||||||
|
|
||||||
--===========================================
|
--===========================================
|
||||||
--
|
--
|
||||||
|
@ -27,4 +27,4 @@ REFERENCES bulk_sources.nlud_classification_order_group ("level");
|
|||||||
ALTER TABLE buildings ADD COLUMN IF NOT EXISTS original_landuse_class text ARRAY[250];
|
ALTER TABLE buildings ADD COLUMN IF NOT EXISTS original_landuse_class text ARRAY[250];
|
||||||
|
|
||||||
-- Land use order, singular. Client and db constrained.
|
-- Land use order, singular. Client and db constrained.
|
||||||
ALTER TABLE buildings ADD COLUMN IF NOT EXISTS original_landuse_order;
|
ALTER TABLE buildings ADD COLUMN IF NOT EXISTS original_landuse_order text;
|
||||||
|
Loading…
Reference in New Issue
Block a user