Jump to content

Is it okay to create table for each user?


cary1234

Recommended Posts

I want to create a website that records whether the user is present or absent during a meeting. The problem is, I'm having difficulty how to create my database structure. 

Each employee has a different meetings, and I see all the employee, date of their meeting and their status.

Something like this.

Example.

Cary

09/12/2013 - present

09/13/2013 - absent

09/18/2013 - absent

 

 

Stanlee

09/12/2013 - absent

09/14/2013 - present

09/19/2013 - present

Is it okay to create table for each user?

No.

 

All you have is the employee, date, and status. Why not a table with the employee, date, and status? Even better, why not a table that lists out all the employees, gives them some ID numbers so it's easier to refer to them in the database, and then a table with the employee ID, date, and status?

employees

id | employee
---+---------
 1 | Cary
 2 | Stanlee

meetings

employee | date       | status
---------+------------+-------
       1 | 09/12/2013 | present
       1 | 09/13/2013 | absent
       1 | 09/18/2013 | absent
       2 | 09/12/2013 | absent
       2 | 09/14/2013 | present
       2 | 09/19/2013 | present

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.