log backend/doc/schema/postgresql-minfo.sql @ 9293:e3e465766cfe

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-17 Tom Gottfried (issue1750) There can be only one SQ-relation of a parameter for a time range (given by sq_relation_id) per station and some other attributes might be null.
2015-04-08 Tom Gottfried (issue1763) Use more distinct constraint names and adapt drop-script.
2015-03-27 Tom Gottfried Enforce strings we rely on.
2015-03-27 Tom Gottfried SCHEMA CHANGE: Remove unnecessary direct relation of sq_relation with rivers.
2015-02-16 Tom Gottfried Meta-data on sounding width associated to bed heights is redundant to real data associated to values.
2015-02-16 Tom Gottfried Bed heights are just bed heights since a while ('single' is obsolete).
2015-02-16 Tom Gottfried Morphological width imported and stored with heights is redundant to table morphologic_width.
2014-10-15 Tom Gottfried SCHEMA CHANGE: 'comment' is not acceptable as column name for Oracle.
2014-10-15 Tom Gottfried SCHEMA CHANGE: removed superfluous columns station and river_id from measurement_stations and adapted other components accordingly.
2014-08-06 Tom Gottfried SCHEMA CHANGE: rename database tables from yield to load_ls according to respective classes.
2014-07-18 Tom Gottfried SCHEMA CHANGE and Importer: get time intervals of SQ-relations from metalines in sediment load files.
2014-07-14 Tom Gottfried SCHEMA CHANGE and Importer (only longitudinal section data so far): only grain fractions given now in schema are valid. We are handling sediment loads, not yields.

http://dive4elements.wald.intevation.org