[Dive4elements-commits] [PATCH] re-added spatial indices for Oracle that work since importer forces correct dimensions

[Wald Commits]

# HG changeset patch
# User Tom Gottfried <tom at intevation.de>
# Date 1363883861 -3600
# Node ID 7b35f2c070c3f0715cdbd4184138a56b7d565ad7
# Parent  6d80318e8858d1c4bc8b7c38f3373857434cc81a
re-added spatial indices for Oracle that work since importer forces correct dimensions

diff -r 6d80318e8858 -r 7b35f2c070c3 flys-backend/doc/schema/oracle-spatial_idx.sql
--- a/flys-backend/doc/schema/oracle-spatial_idx.sql	Thu Mar 21 16:29:54 2013 +0100
+++ b/flys-backend/doc/schema/oracle-spatial_idx.sql	Thu Mar 21 17:37:41 2013 +0100
@@ -1,12 +1,8 @@
--- TODO: index prevents `DELETE FROM rivers' on 11g
--- Error: "Ebenendimensionalitat stimmt nicht mit Geometrie-Dimensionen uberein"
--- CREATE INDEX river_axes_km_spatial_idx ON river_axes_km(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=point');
+CREATE INDEX river_axes_km_spatial_idx ON river_axes_km(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=point');
 
 CREATE INDEX buildings_spatial_idx ON buildings(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=LINE');
 
--- TODO: index prevents `DELETE FROM rivers' on 11g
--- Error: "Ebenendimensionalitat stimmt nicht mit Geometrie-Dimensionen uberein"
--- CREATE INDEX fixpoints_spatial_idx ON fixpoints(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=POINT');
+CREATE INDEX fixpoints_spatial_idx ON fixpoints(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=POINT');
 
 CREATE INDEX river_axes_spatial_idx ON river_axes(GEOM) indextype IS MDSYS.SPATIAL_INDEX parameters ('LAYER_GTYPE=MULTILINE');
 
diff -r 6d80318e8858 -r 7b35f2c070c3 flys-backend/doc/schema/postgresql-spatial.sql
--- a/flys-backend/doc/schema/postgresql-spatial.sql	Thu Mar 21 16:29:54 2013 +0100
+++ b/flys-backend/doc/schema/postgresql-spatial.sql	Thu Mar 21 17:37:41 2013 +0100
@@ -110,7 +110,6 @@
 CREATE TABLE dem (
     id       int PRIMARY KEY NOT NULL,
     river_id int REFERENCES rivers(id) ON DELETE CASCADE,
-    -- XXX Should we use the ranges table instead?
     name             VARCHAR(64),
     range_id         INT REFERENCES ranges(id),
     time_interval_id INT REFERENCES time_intervals(id),