Timeline for Single-Table vs. Multi-Table design
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2020 at 18:54 | comment | added | Tim Davis | Its funny to ask a question, get an answer, then disregard it.. I came along in the same boat, but I agree with OP. I dont want to have to create a table for every post type or user action type. Also this lends well to NoSql databases if one should require one in the future this table could be easily "moved" and distributed or sharded. | |
| Dec 9, 2018 at 6:13 | vote | accept | 2hamed | ||
| Nov 11, 2015 at 8:26 | comment | added | 2hamed | Thanks, but the more I think I am more convinced to go with the first schema. Having many tables just to store post data only leads to bigger queries and multiple joins without saying that introducing new post types can be problematic whereas using a single table I can manage several post types without the need to alter the structure. | |
| Nov 10, 2015 at 14:37 | history | answered | David Spillett | CC BY-SA 3.0 |