# HG changeset patch
# User Hans Plum <hans.plum@intevation.de>
# Date 1315900958 0
# Node ID d6520d46edb7e1bab3dfea8647e8bfec704b0930
# Parent  f68a0504dfb631ba910567a788e7054ff2ec9f58
Removed table boundarypolys because of wrong placed dataset

flys-backend/trunk@2715 c6561f87-3c4e-4783-a992-168aeb5c3f6f

diff -r f68a0504dfb6 -r d6520d46edb7 flys-backend/doc/schema/postgresql-spatial.sql
--- a/flys-backend/doc/schema/postgresql-spatial.sql	Mon Sep 12 13:20:05 2011 +0000
+++ b/flys-backend/doc/schema/postgresql-spatial.sql	Tue Sep 13 08:02:38 2011 +0000
@@ -103,17 +103,6 @@
 SELECT AddGeometryColumn('catchment','geom',31466,'POLYGON',2);
 ALTER TABLE catchment ALTER COLUMN id SET DEFAULT NEXTVAL('CATCHMENT_ID_SEQ');
 
--- Hydrologie/Einzugsgebiete/b1-polygon.shp
-   -- Nur fuer saar vorhanden
-   -- IDEE alle Begrenzungspolygone in eine Tabelle.
-CREATE SEQUENCE BOUNDARYPOLYS_ID_SEQ;
-CREATE TABLE boundarypolys (
-    id int PRIMARY KEY NOT NULL,
-    river_id int REFERENCES rivers(id)
-);
-SELECT AddGeometryColumn('boundarypolys','geom',31466,'MULTIPOLYGON',2);
-ALTER TABLE boundarypolys ALTER COLUMN id SET DEFAULT NEXTVAL('BOUNDARYPOLYS_ID_SEQ');
-
 -- Hydrologie/HW-Schutzanlagen
 -- Wird nicht benoetigt, stattdessen verwenden wir
 -- Gewaesser/Saar/Geodaesie/Linien/rohre-und-sperren.shp