Re: Best practices for aggregate table design

Thanks for your response.  One more follow-up question.

Is there a best practice when to create a measure that includes a
property/dimension?

Let me give an example, say in my example where I have outbound and inbound
calls.

Is is best to have measures:
 -total_inbound
 -total_outbound

OR a dimension 'type' with values outbound/inbound and a single measure
column 'total' ?

I think i would have more rows but fewer columns.  Perhaps it depends upon
the number of possible options there would be (e.g. is it always just
outbound/inbound or would they ever grow further)



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