Search Postgresql Archives

Re: Best practices for aggregate table design

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David G Johnston wrote
> Nabble has a "quote" feature - please use it.
> 
> On Thu, Oct 8, 2015 at 5:00 PM, droberts <

> david.roberts@

> > wrote:
> 
>> I haven't but wouldn't it be better to wait and just add new columns
>> if/when
>> I need to?
>>
> 
> ​Its worth keeping in the back of your mind but I tend to think that
> choosing hstore in order to "be flexible" is a solution looking for a
> problem.  The dynamics between your system and the source system will play
> a large role in determining whether to use a mini-table-within-a-table in
> your model.
> 
> David J.
>


Thanks for everyone's help.  Can anyone recommend a good book on database
modeling, around these 'cube' or aggregate concepts in particular?  I'm
using Postgres but shouldn't matter too much I assume. 

Thanks



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


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux