Mercurial > dive4elements > river
changeset 2803:cdc084071c14
Adapted the column type of relation 'dem' in oracle-spatial schema.
flys-backend/trunk@4160 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author | Ingo Weinzierl <ingo.weinzierl@intevation.de> |
---|---|
date | Mon, 19 Mar 2012 06:11:38 +0000 |
parents | 3fdac7b43dac |
children | 68d1661a57cf |
files | flys-backend/ChangeLog flys-backend/doc/schema/oracle-spatial.sql |
diffstat | 2 files changed, 8 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- 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 <ingo@intevation.de> +2012-03-19 Ingo Weinzierl <ingo@intevation.de> + + * 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 <ingo@intevation.de> * src/main/java/de/intevation/flys/model/Floodmaps.java: Set geometry type to 'Geometry', because Oracle can save POLYGONS and MULTIPOLYGONS in the
--- 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) );