Re: Best practices for aggregate table design

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.