> Yes, this is known as eg. Entity-Attribute-Value model (cf.
> wikipedia).
Thank you for the pointer and term. This will get me started.
> IMO most times its disadvantages (it can be very hard to write
> performant queries compared to the traditional row based model) weigh
> higher than you gain (in flexibility) in relational databases. But it
> sure has its uses cases.
Obviously, I will have to think it through more...
Vlad
