# HG changeset patch
# User Felix Wolfsteller <felix.wolfsteller@intevation.de>
# Date 1363260269 -3600
# Node ID f6478773a5bb2c8f87932a55aa6c910d331e977f
# Parent  b0f14ff573d710017ac2408d7aa17ede4bf73d7c
postgresql-spatial.sql: Fixed table definition.

diff -r b0f14ff573d7 -r f6478773a5bb flys-backend/doc/schema/postgresql-spatial.sql
--- 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),