3 ms·
Yes, in general it is pretty common for web developers to misuse relational databases as key-value stores. There's a common misconception that "joins are slow"
by asdasf 13y ago
Yes, in general it is pretty common for web developers to misuse relational databases as key-value stores. There's a common misconception that "joins are slow", so people write the joins in their application code instead, thus making it several orders of magnitude slower.
- Shorel 13y agoIn the case of Postgres, it has indexable json and hstore datatypes that enable the use of a table as a key-value store. And, it has good performance when compared to MongoDB: http://thebuild.com/presentations/pg-as-nosql-pgday-fosdem-2013.pdf http://thebuild.com/presentations/pg-as-nosql-pgday-fosdem-2... So in this case, it is using Postgres as intended by the datatype designers. May be you are thinking of the Ruby Rails ORMs.
- asdasf 13y agoI didn't mean people using hstore, I mean people having relational data, putting it in tables like you would with a normal relational model, but just not using foreign keys and joins because they mistakenly think "joins are slow".