Any preferences?
From: The Natural Philosopher <tnp_at_invalid.invalid>
Date: Thu, 21 Sep 2017 21:52:13 +0100
Message-ID: <oq18pu$dr2$1_at_dont-email.me>
Scenario:
Date: Thu, 21 Sep 2017 21:52:13 +0100
Message-ID: <oq18pu$dr2$1_at_dont-email.me>
Scenario:
[Quoted] 2000+ data stations, all being polled half hourly or thereabouts.
Each station returns two values, it's measurement, and when it was taken.
Metadata associated with each station is already stored in a different table. Including a unique ID.
Problem: How to store information for these stations
Possibilities
one table with 4000+ columns...
[Quoted] 2000+ tables....of two or three columns
[Quoted] Or is it sensible to have a really simple table with id,station_id,value,time fields and an indices on staion_id, time to enable search by station time series or search by time for a selections of stations?
[Quoted] Or have you a better idea?
I can't seem to find the optimal way to create a 3D database..
-- The biggest threat to humanity comes from socialism, which has utterly diverted our attention away from what really matters to our existential survival, to indulging in navel gazing and faux moral investigations into what the world ought to be, whilst we fail utterly to deal with what it actually is.Received on Thu Sep 21 2017 - 22:52:13 CEST