Re: Best practices for aggregate table design

From: droberts <david(dot)roberts(at)riverbed(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Best practices for aggregate table design
Date: 2015-10-07 20:02:56
Message-ID: 1444248176109-5869195.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I see the advantage is for the developer. We right one REST API call that
leverages this single table regardless whether he wants groups by city for a
month or total for a month. Creating a separate table would make the
backend a bit more complex is all and wouldn't save on space I don't think.

--
View this message in context: http://postgresql.nabble.com/Best-practices-for-aggregate-table-design-tp5868940p5869195.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ramalingam, Sankarakumar 2015-10-07 20:07:18 Re: postgres standby won't start
Previous Message Scott Mead 2015-10-07 19:46:28 Re: backup.old