Skip to main content

This is very much a noob question, so please bear with me. Before 2 weeks, I didn't know what a database meant.

Consider a web application with 100,000 users. Each user can create entries or blog posts, as you may call it. Assume Assume each user has 100 entries. 

Would it be appropriate to store all the users in one table? (Meaning, a table with 100,000 rows?) and further have another table to store the entries made by each user.?

Is this a bad design? What would be an efficient way to store all the information to facilitate quick access of the information?

Thanks for your time!

This is very much a noob question, so please bear with me. Before 2 weeks, I didn't know what a database meant.

Consider a web application with 100,000 users. Each user can create entries or blog posts, as you may call it. Assume each user has 100 entries. Would it be appropriate to store all the users in one table? (Meaning, a table with 100,000 rows?) and further have another table to store the entries made by each user.

Is this a bad design? What would be an efficient way to store all the information to facilitate quick access of the information?

Thanks for your time!

Consider a web application with 100,000 users. Each user can create blog posts. Assume each user has 100 entries. 

Would it be appropriate to store all the users in one table, with another table to store the entries made by each user?

Is this a bad design? What would be an efficient way to store all the information to facilitate quick access of the information?

Source Link

Questions about Database Design for a Web Application

This is very much a noob question, so please bear with me. Before 2 weeks, I didn't know what a database meant.

Consider a web application with 100,000 users. Each user can create entries or blog posts, as you may call it. Assume each user has 100 entries. Would it be appropriate to store all the users in one table? (Meaning, a table with 100,000 rows?) and further have another table to store the entries made by each user.

Is this a bad design? What would be an efficient way to store all the information to facilitate quick access of the information?

Thanks for your time!