Database Structure

Database Structure

Table 1 -- users

The user table stores the information of every university. Each university has to register a unique account and use the name of the university as the login name. The segments of this table are listed as follows:

• school: Name of the university.
• leader: Name of the leader.
• tel: The phone number of the leader.
• mail: The e-mail address of the leader.
• id: A unique ID generated by the system to recognise the school.
• password: The password of the user.
• bill: The quantity of money this university has to pay.
• paid: Whether this university has paid the bill.

Table 2 -- people

The people table stores the information of all the people who are about to come to the race. The segments of this table are listed as follows:

• name: The name of the person.
• idcard: The number of his or her ID card.
• gender: The gender.
• school_id: The ID of the university this person is from.
• accommodation: Whether this person takes the accommodation service.
• meal: Whether this person takes the meal provided by the committee.
• race: The type of individual race this person will take part in. 0 for none, 1 for male pro, 2 for male, 3 for female.
• team_id: The id of the team in which this person is going to participate in the team race. 0 for none.
• id: A unique ID generated by the system to recognise the person.
• deleted: Whether this person is deleted.

Table 3 -- team

The team table stores the information of all the teams and their members. The segments of this table are listed as follows:

• id: A unique ID generated by the system to recognise the team.
• first: ID of the first athlete.
• second: ID of the second athlete.
• third: ID of the third athlete.
• school_id: ID of the school.
• deleted: Whether this team is deleted.