From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | "Vladimir S(dot) Petukhov" <vladimir(at)sycore(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Need help to organize database |
Date: | 2004-12-21 22:00:25 |
Message-ID: | 20041221220025.GA17044@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 22, 2004 at 00:16:06 +0000,
"Vladimir S. Petukhov" <vladimir(at)sycore(dot)org> wrote:
> On Tuesday 21 December 2004 21:21, Bruno Wolff III wrote:
> > On Tue, Dec 21, 2004 at 20:47:31 +0000,
> >
> > "Vladimir S. Petukhov" <vladimir(at)sycore(dot)org> wrote:
> > > 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
> > > );
> >
> > That approach is reasonable but depending on what the val* columns mean
> > you might each of those as a separate role. You didn't add a lot of
> > information, but that they appear to be the same type suggests that you
> > might want one row per value. But without knowing what they mean it is
> > hard to say.
>
> OK, i want to store ststistic information, ingoing/outgoing traffic,
> ingoing/outgoing errors(val1-val4) for example...
Those sound like different domains then for each column. So you probably do
want to keep the 8 values in one row.
I also noticed that you marked a lot of these values as NULL. I think that
daypos, hourpos and id form the primary key and you probably don't want to
allow NULLs for these.
From | Date | Subject | |
---|---|---|---|
Next Message | Doug Quale | 2004-12-21 22:13:46 | Re: PostgreSQL training curriculum |
Previous Message | Jim C. Nasby | 2004-12-21 21:36:10 | PostgreSQL training curriculum |