Re: Mapping arbitrary number of attributes to DB
Date: Mon, 23 Oct 2006 12:00:34 -0800
Message-Id: <453d126a$0$19727$88260bb3_at_free.teranews.com>
Cimode wrote:
> > Here it is: the application is going to be importing data from files
> > that contain sensor readings. These files can have an arbitrary number
> > of columns, anywhere from maybe three or four all the way up to 200+
> > depending
> No need to go any further to tell you this is the wrong direction
And David Portas wrote:
> I would have expected the file to be no more than a convenient medium
> for interchanging the data. In that case the file structure is surely
> the least relevant part of the problem - yet you have apparently based
> your whole model around it!
>
> The route to an effective logical design is via an understanding of the
> concepts you are trying to model. I don't think columns in files will
> help achieve that. Even given the limited information you supplied your
> design still looks highly impractical.
Sadly enough, I agree with both of you. The problem is, part of the way the data is represented is out of my control. Data is coming in from weather stations. Some of these stations may have 1 sensor (e.g. temperature), some of these stations may have many sensors (temperature, wind speed, soil temperature, humidity, air pressure, many of them redundant). Thus, each station can have a number of attributes that vary from one to dozens. I can't tell the scientists "You may have 32 sensors per station, no more, no less." That just won't work, for reasons I hope are obvious. :)
j
-- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE -- Posted via a free Usenet account from http://www.teranews.comReceived on Mon Oct 23 2006 - 22:00:34 CEST
