Ok, this is a real example:
CREATE TABLE account (
val1 BIGINT NULL,
val2 BIGINT NULL,
...
daypos SMALLINT NULL, -- Day position
hourpos SMALLINT NULL, -- Hour position
id INT NULL -- Link to the object
);
On Tuesday 21 December 2004 14:38, Bruno Wolff III wrote:
> On Mon, Dec 20, 2004 at 12:13:31 +0000,
>
> "Vladimir S. Petukhov" <vladimir@sycore.org> wrote:
> > Hi
> > Sorry for my English..
> >
> > I need to organize database structure for saving statistic data for
> > objects. I have about 24 * 31 * 4 fields (4 month, 31 days, 24 hours) of
> > data for one object. Each field contain 8 numbers (N in general). So:
> > object1 -> data -> field1, field2,...
> > object2 -> data -> field1, field2,...
> > ...
> > How can I store this data in postgres database?
> >
> > For example it may be 24 * 31 * 4 * 8 fields and 1 row per object in
> > table - but it is not good idea, of course.
> >
> > Or may be 8 fields and 24 * 31 * 4 rows per object in table, but table
> > looked very big...
>
> You want to store rows with an object id, a field or fields storing the
> hour and the 8 object fields (assuming these fields shouldn't also
> be one per row - but without any more knowledge about them I can't say).
> You should put a primary key constraint on the object id and the hour
> field(s).
>
> > Or may be it's not good idea to use postgres for this purpose?
>
> Without seeing what you are going to do with the data it is hard to say
> if using a dbms is overkill or not.
--
Riches cover a multitude of woes.
-- Menander
Now playing: track08.mp3
AutoGenerated by fortune & xmms...
