[PATCH] Precision and scale have to be set to represent integers with NUMBER; DOUBLE PRECISION is preferable for floating point (see issue1304)
Wald Commits
scm-commit at wald.intevation.org
Tue May 13 15:33:55 CEST 2014
# HG changeset patch
# User Tom Gottfried <tom at intevation.de>
# Date 1399969800 -7200
# Node ID 0c74b5f8de170e428b0368e49a9d3c2d55ff435d
# Parent 8d4a4c645e61636d020c4971b9e57cff3ad9c940
Precision and scale have to be set to represent integers with NUMBER; DOUBLE PRECISION is preferable for floating point (see issue1304).
diff -r 8d4a4c645e61 -r 0c74b5f8de17 backend/doc/schema/oracle-minfo.sql
--- a/backend/doc/schema/oracle-minfo.sql Thu May 08 15:26:32 2014 +0200
+++ b/backend/doc/schema/oracle-minfo.sql Tue May 13 10:30:00 2014 +0200
@@ -150,11 +150,11 @@
CREATE SEQUENCE POROSITY_ID_SEQ;
CREATE TABLE porosity (
- id NUMBER NOT NULL,
- river_id NUMBER NOT NULL,
- depth_id NUMBER NOT NULL,
+ id NUMBER(38,0) NOT NULL,
+ river_id NUMBER(38,0) NOT NULL,
+ depth_id NUMBER(38,0) NOT NULL,
description VARCHAR(256),
- time_interval_id NUMBER NOT NULL,
+ time_interval_id NUMBER(38,0) NOT NULL,
PRIMARY KEY(id),
CONSTRAINT fk_p_river_id FOREIGN KEY (river_id) REFERENCES rivers(id) ON DELETE CASCADE,
CONSTRAINT fk_p_depth_id FOREIGN KEY (depth_id) REFERENCES depths(id),
@@ -165,11 +165,11 @@
CREATE SEQUENCE POROSITY_VALUES_ID_SEQ;
CREATE TABLE porosity_values (
- id NUMBER NOT NULL,
- porosity_id NUMBER NOT NULL,
- station NUMBER NOT NULL,
- shore_offset NUMBER,
- porosity NUMBER NOT NULL,
+ id NUMBER(38,0) NOT NULL,
+ porosity_id NUMBER(38,0) NOT NULL,
+ station DOUBLE PRECISION NOT NULL,
+ shore_offset DOUBLE PRECISION,
+ porosity DOUBLE PRECISION NOT NULL,
description VARCHAR(256),
PRIMARY KEY(id),
CONSTRAINT fk_pv_porosity_id FOREIGN KEY(porosity_id) REFERENCES porosity(id) ON DELETE CASCADE
More information about the Dive4Elements-commits
mailing list