Re: Best practices for aggregate table design - Mailing list pgsql-general

From Marc Mamin
Subject Re: Best practices for aggregate table design
Date
Msg-id B6F6FD62F2624C4C9916AC0175D56D88420965FF@jenmbs01.ad.intershop.net
Whole thread Raw
In response to Best practices for aggregate table design  (droberts <david.roberts@riverbed.com>)
Responses Re: Best practices for aggregate table design  (droberts <david.roberts@riverbed.com>)
List pgsql-general
>2. I'm adding a 'null' row to show all the calls for a given month
>regardless of city or state, again to simplify the client side. It adds a
>row and is somewhat sparse but preferrable by the developer. Acceptable
>practice?

do you see any advantage with this model?
I would store your monthly data within a separate table.

regards,
Marc Mamin

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: backup.old
Next
From: Steve Pribyl
Date:
Subject: Re: backup.old