Re: Best practices for aggregate table design

From: Marc Mamin <M(dot)Mamin(at)intershop(dot)de>
To: droberts <david(dot)roberts(at)riverbed(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best practices for aggregate table design
Date: 2015-10-07 19:27:41
Message-ID: B6F6FD62F2624C4C9916AC0175D56D88420965FF@jenmbs01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Steve Pribyl 2015-10-07 19:29:10 Re: backup.old
Previous Message David G. Johnston 2015-10-07 19:25:48 Re: backup.old