changeset 5289:f6478773a5bb

postgresql-spatial.sql: Fixed table definition.
author Felix Wolfsteller <felix.wolfsteller@intevation.de>
date Thu, 14 Mar 2013 12:24:29 +0100 (2013-03-14)
parents b0f14ff573d7
children 394841a66c14 3dc4c2798212
files flys-backend/doc/schema/postgresql-spatial.sql
diffstat 1 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/flys-backend/doc/schema/postgresql-spatial.sql	Thu Mar 14 12:24:06 2013 +0100
+++ b/flys-backend/doc/schema/postgresql-spatial.sql	Thu Mar 14 12:24:29 2013 +0100
@@ -112,8 +112,8 @@
     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);
+    range_id         INT REFERENCES ranges(id),
+    time_interval_id int REFERENCES time_intervals(id),
     projection       VARCHAR(32),
     srid	    int  NOT NULL,
     elevation_state  VARCHAR(32),

http://dive4elements.wald.intevation.org