Hi
I'm looking at designing a simple holiday/vacation request system online for my team at work.
Initially, I want to simply start by offering the normal user two options - a list of their holiday requests with a running total of holiday days left, and a holiday request form which when submitted will have a status of 'awaiting authorisation' and an email sent to the line manager. Obviously the line manager will then be able to login to set the status of the request to Approved or Declined (or any other status).
What I what is some advice on the DB structure.
I was thinking of a USERS table for users to login, a STATUS table, an AUTHORISORS table and then a REQUESTS table.
Does this sound about right?
Have I missed anything obvious?
I'm looking at designing a simple holiday/vacation request system online for my team at work.
Initially, I want to simply start by offering the normal user two options - a list of their holiday requests with a running total of holiday days left, and a holiday request form which when submitted will have a status of 'awaiting authorisation' and an email sent to the line manager. Obviously the line manager will then be able to login to set the status of the request to Approved or Declined (or any other status).
What I what is some advice on the DB structure.
I was thinking of a USERS table for users to login, a STATUS table, an AUTHORISORS table and then a REQUESTS table.
Does this sound about right?
Have I missed anything obvious?