4 ms·
I think the question is how does that compare to the usual trick of adding a key/value/attribute table? create table misc_attrs (maintable_id foreign key, na
by tedunangst 13y ago
I think the question is how does that compare to the usual trick of adding a key/value/attribute table?
create table misc_attrs (maintable_id foreign key, name text, value text)
- simonw 13y agoWhen reading data back, it's more efficient to query a single table than to have to join against an extra attributes table See https://news.ycombinator.com/item?id=6574269 https://news.ycombinator.com/item?id=6574269 for anecdotal evidence.
- moron4hire 13y agothere are so many variables in that anecdote that there is nothing that can be gleaned from it.
- Herbert2 13y agoAlright, these were approximately the fields that were Postgre-fied. CREATE TABLE event ( "references" text[], (was 2 tables, references and reference_on_event) "entities" text[], (ditto) "actors" text[], (ditto) "targets" text[], (ditto) "payload" json, (EAV) ) Gin index on all the text arrays. There are about 150k events saved per day and PostgreSQL is running on the same kinds of hardware as SQL Server was. The application is quite read heavy.
- einhverfr 13y agoThere are times actually I find it helpful to break 1NF in PostgreSQL. This is certainly not free but it really helps some sorts of queries, and it avoids having to do a sort of pseudo-EAV to get certain things working.