log backend/doc/schema/postgresql.sql @ 9097:82917e414d76

age author description
2018-04-03 mschaefer Datatype changes from rev 8942 reverted
2018-03-13 mschaefer Same data types, precision and scale as in Oracle (as far as possible)
2015-04-15 Tom Gottfried (issue1796) We don't necessarily need the river Rhine. SedDB river names are purely optional.
2015-04-13 Andre Heinecke (issue 1796) Scheme change! Add model for seddb_name lookup table.
2015-04-02 Tom Gottfried Whitespace-cleanup schema files.
2014-10-15 Tom Gottfried SCHEMA CHANGE: There is no boolean data type in oracle, and therefore it's no good idea to use it in postgresql.
2014-02-07 Tom Gottfried Schema correction following yesterday's brain failure.
2014-02-06 Tom Gottfried SCHEMA CHANGE: renamed uuid-column to avoid collision with data type.
2014-02-06 Tom Gottfried SCHEMA CHANGE: Add UUIDs to rivers.
2013-09-12 Tom Gottfried SCHEMA CHANGE: a < b now enforced on ranges. double-precision
2013-08-19 Tom Gottfried Undo misguided schema change from r5207 double-precision
2013-08-12 Tom Gottfried fixed syntax errors in Postgres-schema. double-precision
2013-06-28 Tom Gottfried Schema change: add new field 'source' to wst_columns, currently only for official lines double-precision
2013-06-12 Sascha L. Teichmann Backend: Modified schema for a better model of official lines.
2013-06-04 Felix Wolfsteller Remove stray semicolon from sql schema.
2013-05-31 Tom Gottfried Schema change: remove UNIQUE-constraint which allows importing cross sections only from PRF
2013-05-23 Tom Gottfried Schema change: view for WSTs which deales with multiple ranges matching station (issues 1315 and 1296)
2013-05-16 Tom Gottfried Schema change: Add missing constraints to cross sections in Oracle, cosmetics
2013-05-13 Tom Gottfried backout 6009:6ea171b6d8d2 because this was only really valid for fixations
2013-05-13 Tom Gottfried Schema change because WST-columns without time interval are useless
2013-05-08 Tom Gottfried Schema change: leave it up to AFT whether time intervals are unique per gauge but do not accept duplicate bfg_id per gauge
2013-05-07 Tom Gottfried Schema change: named_main_values.name is not unique, as we can have the same name for different types
2013-05-03 Tom Gottfried Schema change: make gauges.official_number unique per river as we can have multiple identical gauges for different representations of the same river. Comments and TODOs
2013-05-03 Tom Gottfried Schema change: remove UNIQUE-constraint from rivers.official number as we have different representations of the same river (e.g. for sommer and winter)
2013-04-30 Tom Gottfried Schema change: add constraint to discharge tables
2013-04-25 Sascha L. Teichmann Rename modules to more fitting names. base flys-backend/doc/schema/postgresql.sql@fd123768e5ac

http://dive4elements.wald.intevation.org