Database design of personal calendar

  1. question: personal calendar, is there one table per user or one table for all users, or is there any other way?
  2. my idea: each user has a table with the account number as the table name. When querying, you can find his schedule information according to the user"s account number. Is this method feasible? Getting started with the database. I feel that this method is a little out of date.
Apr.15,2022

if there are few users, one table per user is OK, for example, this is a personal system with only three or five users.
the normal idea is, of course, to put a table in one table. It is difficult to maintain a table for each user. If you have hundreds of thousands of users and build hundreds of thousands of tables, you have to write a script if you want to add a field. If the user account conflicts with other table names or is the same as keywords, you have to deal with it. Then the boss asks you to find out who didn't write down the schedule today, and there will be no results in a few minutes.
in short, look at the requirements.

Menu