| Wed, 08 Apr 2015 18:15:55 +0200 |
Tom Gottfried |
(issue1763) Use more distinct constraint names and adapt drop-script.
|
| Thu, 02 Apr 2015 17:17:51 +0200 |
Tom Gottfried |
Whitespace-cleanup schema files.
|
| Mon, 16 Feb 2015 11:48:05 +0100 |
Tom Gottfried |
Meta-data on sounding width associated to bed heights is redundant to real data associated to values.
|
| Mon, 16 Feb 2015 11:08:33 +0100 |
Tom Gottfried |
Bed heights are just bed heights since a while ('single' is obsolete).
|
| Mon, 16 Feb 2015 09:00:08 +0100 |
Tom Gottfried |
Morphological width imported and stored with heights is redundant to table morphologic_width.
|
| Wed, 15 Oct 2014 19:48:20 +0200 |
Tom Gottfried |
SCHEMA CHANGE: 'comment' is not acceptable as column name for Oracle.
|
| Wed, 15 Oct 2014 19:20:26 +0200 |
Tom Gottfried |
SCHEMA CHANGE: removed superfluous columns station and river_id from measurement_stations and adapted other components accordingly.
|
| Wed, 06 Aug 2014 19:17:12 +0200 |
Tom Gottfried |
SCHEMA CHANGE: rename database tables from yield to load_ls according to respective classes.
|
| Fri, 18 Jul 2014 18:01:49 +0200 |
Tom Gottfried |
SCHEMA CHANGE and Importer: get time intervals of SQ-relations from metalines in sediment load files.
|
| Mon, 14 Jul 2014 15:36:44 +0200 |
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.
|
| Wed, 09 Jul 2014 15:56:15 +0200 |
Tom Gottfried |
Repair last commit.
|
| Wed, 09 Jul 2014 15:51:31 +0200 |
Tom Gottfried |
SCHEMA CHANGE: consistent naming scheme and drop script for sediment load at measurement stations.
|
| Tue, 08 Jul 2014 19:44:54 +0200 |
Tom Gottfried |
SCHEMA CHANGE: Added new structure for sediment loads measured at measurement stations.
|
| Tue, 10 Jun 2014 15:11:36 +0200 |
Tom Gottfried |
SCHEMA CHANGE: Removed bed height epochs.
|
| Tue, 13 May 2014 10:30:00 +0200 |
Tom Gottfried |
Precision and scale have to be set to represent integers with NUMBER; DOUBLE PRECISION is preferable for floating point (see issue1304).
|
