3 ms·
Well, this is exactly why competition is good, in every domain. That's why PostgreSQL got its column mode and JSON type, because there was a clear use case for
by nostalgeek 8y ago
Well, this is exactly why competition is good, in every domain. That's why PostgreSQL got its column mode and JSON type, because there was a clear use case for performance for the former and schema-less data for the latter. EAV pattern is a plague and I'm glad documents are replacing it.
- zurn 8y agoWhat do you mean by PG's column mode?
- icebraining 8y agoPostgres has had hstore for schema-less data since 2003.
- igl 8y agoThis is a very blunt statement and overvalues hstore. Keys AND values in hstore are and can only be text strings.
- MarHoff 8y agoWith arrays and composite type the potential for semi-structured schema was there for decades. The concept just got more mainstream with NoSQL, more easy to maintain and more efficient with indexables type such as JSONB.
- zkomp 8y agoYes hstore is limited but since you can represent numbers and even hstore itself as text, all you really have to do is cast to and from text and then you have a nested structure with almost anything in it... jsonb is much better obviously but hstore was really nice and kind of under appreciated.
- amirouche 8y agoWhy EAV is plague? Isn't JSON type a wrapper of EAV?
- nostalgeek 8y agoJSON type is JSON type, EAV isn't a data type, it's a data modelling pattern.
- wild_preference 8y agoYou can see what they were referring to here: https://en.m.wikipedia.org/wiki/Entity–attribute–value_model https://en.m.wikipedia.org/wiki/Entity–attribute–value_model