Timeline for Working on a blog creation website; should I be creating a new table for each blog, or keep everything on the same table?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2015 at 3:20 | answer | added | Rick James | timeline score: 1 | |
| May 23, 2015 at 19:44 | comment | added | Aaron Bertrand | Or thousands of different tables, why is the latter less complicated than the former? | |
| May 23, 2015 at 19:15 | comment | added | Kurt | I meant the creation of database for every blog. I'll end up with thousands of different databases, won't I? | |
| May 23, 2015 at 18:41 | comment | added | Aaron Bertrand | What's complicated? You have the same code running in the context of each database, or the code has to know the context of which table to use. Something in there is going to be "complicated" as soon as you go from one blog to two. | |
| May 23, 2015 at 18:32 | comment | added | Kurt | Hmm. It sounds a bit complicated to be honest. I'll look into it though. Thanks! | |
| May 23, 2015 at 18:26 | comment | added | Aaron Bertrand | You should probably have a database per blog. Then you don't have to dynamically specify the table name (what are your tables going to be called, blogposts00001, blogposts00002, etc?), and you don't have to worry about the scalability of blowing up a single table. The nice thing about a database per blog is when one blog posts a ton of content it's easier to move a single database to a different server or storage than to move a singe table or some subset of a table. | |
| May 23, 2015 at 17:08 | review | First posts | |||
| May 24, 2015 at 15:12 | |||||
| May 23, 2015 at 17:06 | history | asked | Kurt | CC BY-SA 3.0 |