Use case for hstore against multiple columns

Question

I\'m having some troubles deciding on which approach to use.

I have several entity \"types\", let\'s call them A,B and C, who share a certain number of attributes (a

Answer 1

In my line of work, we have rapidly-changing requirements, and we rarely get downtime for proper schema upgrades. Having done both the big-record with lots on nulls and highly normalized (name,value), I've been thinking that it might be nice it have all the common attributes in proper columns, and the different/less common ones in a "hstore" bucket for the rest.