How to design the database of the leave process and how to design the database of the review process

Database is a warehouse that organizes, stores and manages data according to the data structure, and data management is no longer just about storing and managing data, but has transformed into a variety of data management methods required by users. There are many types of databases, from the simplest to store all kinds of data, to large database systems that can store massive amounts of data. In the information-based society, the full and effective management and utilization of all kinds of information resources is a prerequisite for scientific research and decision-making management.

Database technology is the core part of various information systems such as management information system, office automation system, decision support system, etc., and is an important technical means for scientific research and decision-making management. A database is a general data processing system for a unit or an application field, which stores a collection of relevant data belonging to enterprises, business units, groups and individuals. The data in the database is built from a global perspective and is organized, described, and stored according to a certain data model.

Its structure is based on the natural connections between the data, providing all the necessary access paths, and the data is no longer application-specific, but organization-wide, with a holistic structured character. The data in the database is built for many users to share their information, and it has been freed from the limitations and constraints of specific procedures. Different users can use the data in the database in their own usage; Multiple users can share data resources in the database at the same time, that is, different users can access the same data in the database at the same time.

Data sharing not only satisfies the requirements of each user for information content, but also meets the requirements of information communication between users.

Big data refers to the collection of data that cannot be captured, managed, and processed by conventional software tools within a certain time frame, and is a massive, high-growth and diversified information asset that requires new processing modes to have stronger decision-making, insight and process optimization capabilities. The 5V characteristics of big data (proposed by IBM): Volume (mass), Velocity (high-speed), Variety (variety), Value (low value density), Veracity (authenticity), and the platform has Hadoop

Do you want to write a leave of absence project? In what language is it written?

Employee Table: Employee information (employee ID, name, gender, etc.), associated roles (role ID), role table: role classification (role ID, role name).

Leave application form: leave serial number, employee ID, application date, leave start date, number of vacation days, current status (application - "first instance" - "2 trials" approved - not approved).

Leave Flowchart: Leave serial number, approver, approval date, and approval result.

If the function is in the strong point, you can add the approval limit date, and if the limit is not approved, it will be automatically marked as approved and you can expand it.

1. User table.

User ID User Role (1: Salesman, 2: Manager, 3: General Manager, 4: President...) User's name.

2. Customer table.

Customer ID: Customer Name.

3. Salesman customer table.

The user ID (in fact, the user in the user table is the user whose role is the salesman) customer ID

4. The salesman handed over the customer application form.

Applicant user ID

The ID of the customer requesting the handover

Approval status (0: Under Approval, 1: Approved...) Post-handover user ID

5. Leave form.

The start time of the leave for the user ID.

The end time of the leave of absence.

Leave category (1: personal leave, 2: sick leave, 3: marriage leave...) Approval status (0: Under Approval, 1: Approved...)

1. User table.

User ID User Role (1: Salesman, 2: Manager, 3: General Manager, 4: President...)

User's name. 2. Customer table.

Customer ID: Customer Name.

3. Salesman customer table.

User ID (in fact, the user role in the user table is the user who is the salesman), customer ID4, the salesman hands over the customer application form.

Applicant user ID

The ID of the customer requesting the handover

Approval status (0: Under Approval, 1: Approved...)

Post-handover user ID

5. Leave form.

The start time of the leave for the user ID.

The end time of the leave of absence.

Leave category (1: personal leave, 2: sick leave, 3: marriage leave...)

Approval status (0: Under Approval, 1: Approved...)

6. Weekly report.

Weekly report month of user ID.

Approval status (0: Temporary Save, 1: Submitted, 2: Manager Approved, 3: General Manager Shan Chun Approved...)

In fact, the specific control, you have to control the process in the program, and there is no automatic control and elimination as you said, but this kind of table structure design can meet your later needs to no longer move the data lead only knowledge library, just modify the business process.

The design of the database table is carried out on the basis of requirements analysis, first the analysis, then e-r, and then the actual table creation (of course, this step can be done by the ER tool).

Here's the simplest example:

Student Form (records student information).

Faculty table (record counselors, class teachers and other faculty and staff information) approval rule table (determine who approves first, who is the next approver, each approver is represented by a number, such as faculty number, foreign key to faculty table).

Leave application form (number, initiator, reason, start and end time, etc.) and approval process (leave application number, approver, approval time, approval result, reason for remarks, etc.).

I'm also going to do an assignment on the approval system, but it's simpler, just approve students' leave requests. Novice hair doesn't understand, how to do the database?

You can create an independent form for leave, set a field in the form and associate it with the employee number in the employee table, and then you can establish a relationship with the employee table when retrieving and calculating, as for establishing a relationship with other tables, I don't think it's necessary, because leave is nothing more than salary, as long as the field in the leave table has time to start and end to make calculations. Suggestion: id name number reason start end department hou day In this way, the basic information of the leave can be expressed, it is not too troublesome, and it is the best way to complete a matter by a table.

Table A is related to Table B. Table B is a table of foreign keys for C. There are also def tables. G-table. It's all related.

1. User table.

User ID User Role (1: Salesman, 2: Manager, 3: General Manager, 4: President...)

User's name. 2. Customer table.

Customer ID: Customer Name.

3. Salesman customer table.

User ID (in fact, it is the user whose role is the salesman in the user table) customer ID4, the salesman hands over the customer application source orange age table.

Applicant user ID

The ID of the customer requesting the handover

Approval status (0: Under Approval, 1: Approved...)

Post-handover user ID

5. Leave form.

The start time of the leave for the user ID.

The end time of the leave of absence.

Leave category (1: personal leave, 2: sick leave, 3: marriage leave...)

Approval status (0: Under Approval, 1: Approved...) 6. Weekly report.

Weekly report month of user ID.

Approval Status (0: Temporarily Saved, 1: Submitted, 2: Hail Manager Approved, 3: General Manager Approved...)

This kind of design is similar to the translation, which is the most direct method, and of course it is feasible to write rotten. However, I think that in this process, the trigger can be used, and when D agrees (i.e., the state changes), the change to Songkuan can be directly triggered.

Other situations are similar.

A leave management system can be installed with one.

You can go to a CRM system to manage it, or you can do it.

1.Employee information form (including job title (level), entry time (seniority), department, etc.) 2Department Information Table (Grouping Table).

3.Total hours (records the actual number of attendances per month) (employee number, year, January hours, February hours. December working hours).

4.Leave summary table (record the base number of various leaves, the number of days taken, the number of remaining leaves) (employee number, year, annual leave base, the remaining number of days in the previous year, the number of days taken, the number of days not taken, the number of days taken in sick leave, the number of days not taken, the number of days taken on other leaves).

5.Attendance Statement (Employee Number, Date of Attendance, Number of Hours Worked.) 6.Leave schedule (employee number, leave date, leave type, leave hours)7Leave Type Table.

8.Workday table (only need to set the status change, Monday to Friday is considered as a working day by default, and Saturday and Sunday are rest days, for example, October 1 is a Monday, it should be set as a non-working day, if it happens to be a Saturday, it does not need to be set).

9.A table of users (including permission settings, etc.).

tb dept This is your department (department number, department name, tb vaction, holiday type, attendance, various classifications, tb employee, your employees' records, throw in tb attendance attendance records (date, time, who, record check-in markings).

That's probably it, the above 3 are the structure, and the final summary record is good inside.