Timeline for How to store thousands of properties related to a record in PostgreSQL?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2018 at 20:31 | history | edited | Aaron Bertrand | CC BY-SA 3.0 |
Content moved
|
| Jan 22, 2015 at 21:56 | comment | added | András Váczi |
Aaron's post summarizes the possible pitfalls very well. With careful design and planning, this may be a viable solution. It usually has relatively high development costs, as far as I can tell, so using some ready-to-use structures like hstore or jsonb can mean faster delivery. YMMV, as nearly always.
|
|
| Jan 22, 2015 at 21:01 | history | edited | Joishi Bodio | CC BY-SA 3.0 |
added 363 characters in body
|
| Jan 22, 2015 at 20:58 | comment | added | Joishi Bodio | New acronym for me ... looks it up Yes, that is the gist of what I was suggesting. I have no idea about what Dezso may have been commenting about (with being brave) .. I have never used the above model. | |
| Jan 22, 2015 at 17:16 | comment | added | TehNrd | Is this essentially an EAV model? | |
| Jan 22, 2015 at 17:02 | history | answered | Joishi Bodio | CC BY-SA 3.0 |