title: Designing an attendance database: Is it good practice to use employees as fields?
body: <p>I am designing a very simple attendance tracking database, actually this will be my very first database. There are about 30 employees, everyone has a unique id. Every few months, someone quits and there will be some newcomers. The only thing need to be recorded everyday is their attendance status:attendance,absence or leave. </p>
  
  <p>I am thinking to use only one table, the fields are employees' id, and rows represents days, values are either 0,1 or 2. I think this is pretty much it. But one thing I don't feel good is when someone joins, I will have to add a new field for him. In my past experience, a table's fields are always stable, only records are being changed. This makes me wonder whether the design on my mind is a good idea, and if not, what is a good design for this?</p>