Re: Dynamic table

From: A B <gentosaker(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Dynamic table
Date: 2009-06-16 12:56:53
Message-ID: dbbf25900906160556v24826811m1e337009ef56c7a4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/6/16 Greg Stark <gsstark(at)mit(dot)edu>

> On Tue, Jun 16, 2009 at 12:21 PM, A B<gentosaker(at)gmail(dot)com> wrote:
>
> I don't think think it's fair to call this EAV actually. It sounds
> like the integers are a collection of things which represent the same
> thing. Ie, they're all bank balances or all distances driven, just for
> different time periods. Storing all objects representing the same
> thing in the same column is just a regular normalized table, not EAV.
>
> You might want to consider partitioning the table of integers by type
> to facilitate dropping the old ones. But that's an administrative
> trick, not a fundamental schema design decision.

Unfortunatly there is no "type" here. One can make no distinction between
the integers and one can not tell when they are added or dropped.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message A B 2009-06-16 13:02:56 Re: Dynamic table
Previous Message Greg Stark 2009-06-16 11:59:19 Re: Dynamic table