# HG changeset patch # User Ingo Weinzierl # Date 1332137498 0 # Node ID cdc084071c14c70c027d990bbc8671c1b76219ad # Parent 3fdac7b43dac32e7a19c69f9eca9f269176e06b6 Adapted the column type of relation 'dem' in oracle-spatial schema. flys-backend/trunk@4160 c6561f87-3c4e-4783-a992-168aeb5c3f6f diff -r 3fdac7b43dac -r cdc084071c14 flys-backend/ChangeLog --- a/flys-backend/ChangeLog Mon Mar 19 06:09:31 2012 +0000 +++ b/flys-backend/ChangeLog Mon Mar 19 06:11:38 2012 +0000 @@ -1,4 +1,9 @@ -2012-03-16 Ingo Weinzierl +2012-03-19 Ingo Weinzierl + + * doc/schema/oracle-spatial.sql: Set the type of 'lower' and 'upper' column + of relation 'dem' to NUMBER(19,5). + +2012-03-19 Ingo Weinzierl * src/main/java/de/intevation/flys/model/Floodmaps.java: Set geometry type to 'Geometry', because Oracle can save POLYGONS and MULTIPOLYGONS in the diff -r 3fdac7b43dac -r cdc084071c14 flys-backend/doc/schema/oracle-spatial.sql --- a/flys-backend/doc/schema/oracle-spatial.sql Mon Mar 19 06:09:31 2012 +0000 +++ b/flys-backend/doc/schema/oracle-spatial.sql Mon Mar 19 06:11:38 2012 +0000 @@ -142,8 +142,8 @@ ID NUMBER PRIMARY KEY NOT NULL, river_id NUMBER(38), -- XXX Should we use the ranges table instead? - lower NUMBER(38), - upper NUMBER(38), + lower NUMBER(19,5), + upper NUMBER(19,5), path VARCHAR(256), UNIQUE (river_id, lower, upper) );