Dormitory management system based on SpringBoot [with source code]

Dormitory management system based on SpringBoot

  • Development language: Java
  • database: mysql
  • Technology: SpringBoot+MyBatis
  • Tools: IDEA/Ecilpse+mysql+Navicat

Roles: dormitory supervisor, student, administrator

  1. The administrator can manage the information of students and dormitory management in this system, as well as manage buildings, dormitories, and occupancy.
  2. Students can view the students and dormitories in this system, but they do not have permission to modify, add, or delete.
  3. The dormitory management can log in to this system to manage the dormitory, occupancy, students and other information of this system.

insert image description here

insert image description here
insert image description here
insert image description here
insert image description here
insert image description here

1 Introduction

1.1 Research Background

  With the continuous popularization and development of the network, the dormitory management system has developed rapidly relying on the support of network technology. First of all, we must start from the actual needs of administrators and students, and develop targeted dormitory management by understanding the needs of administrators and students. Function, using the convenience and quickness that the current network brings to administrators and students to adjust the system, the designed system makes it more convenient for students to use, the main purpose of this system is to bring convenience to administrators and students, manage The staff can manage the dormitory through the computer without leaving home. At the same time, with the development of e-commerce, the dormitory management system has been loved by the majority of colleges and universities.

  Since the development of the Internet, it has solved many problems that we cannot solve, making our work more convenient and improving our work efficiency. At present, all walks of life are using network information management programs, and different groups of people are also exposed to information management, especially in major e-commerce industries. Through the analysis and summary of the development of the current network environment, the development of the dormitory management system can change the previous dormitory management methods and the state of traditional offline dormitory management. Due to the increasing number of people, the use of traditional dormitory management models is far from being satisfactory. Users demand, and more and more schools are also opening online management, so the development of a dormitory management system can solve the problem that the school is not conducive to offline management. At the same time, the school can use the network to manage ball information. The designed website Ensure the integrity and safety of information, so as to improve work efficiency and ensure the safe and normal operation of the system.

1.2 Research Status

  The development of their information technology in foreign countries is many times that of our country. Since the world's first computer was born in the United States in 1946, foreign information technology has been developing rapidly, and some computer application software has also appeared one after another. Software technology It has also been continuously improved and updated. The software industry has long been everywhere.

  In China, the development of information technology in our country started relatively late, and we slowly and continuously optimized and reformed in the later period, so that our information technology rose to a new stage. Nowadays, the technology of software development can basically reach the level of independent development system application after a lot of research and life practice, and various industries in life also replace software operation with traditional recording mode. The software industry is one of the hottest industries right now.

  As the number of dormitory managers continues to increase, the dormitory management system is also increasing. Due to the increase in dormitory information, the dormitory management system can carry out complete planning and management of dormitory management, and the school also completes the daily management information through the network system. Therefore, the development of the online dormitory management system has brought enough convenience to people. People use the system to meet the needs of life. Therefore, due to the increase in information, the information processing system also increases. modern crowd needs. This development and design is mainly to realize the dormitory management system, combined with java technology and mysql database design, to make up for the shortcomings of the current online ball shopping website, to develop a convenient and practical dormitory management system, and the designed program has The interface is neat and powerful, and overall, the design of the dormitory management system solves the problem of scattered information and is not conducive to dormitory management. The system can be implemented and can be put into the real environment, which can not only solve the above-mentioned problems , making information management more standard.

1.3 Research content

  The development and design of the dormitory management system is based on the actual situation of the user, and the system requirements are analyzed in detail, and then the overall design of the system is carried out. Finally, the system design is more complete through testing, and all functions in the system can be realized. , before starting to write the thesis, I personally went to the library to borrow related books, mysql database books and other programming books, and then for the developed dormitory management system, I went to the Internet to find many systems made by others, and referred to their design results to evaluate my own The system carries out a more detailed system design, lists all the functional results in the system one by one, then conducts demand analysis, and finally codes all the functional modules, and finally completes the overall test of the system to realize the normal operation of the system.
system analysis

3.1 Feasibility analysis

At the beginning of system development, system feasibility analysis should be carried out. The purpose of this is to solve the biggest problem with the least cost. Once the program development meets the needs of users, there will be many benefits. Next, we will consider whether this system is worth developing in terms of technology, operation, and economy.

3.1.1 Technical Feasibility

  The dormitory management system adopts the springboot framework, JAVA programming language and mysql database for development and design. As a computer major student, I have been exposed to a lot of programming knowledge during school, including various programming software, and I have a good understanding of them. It is relatively systematic, so there is still a certain degree of certainty in technology development.

3.1.2 Economic feasibility

  When I designed the system, I mainly started from saving costs, and then carried out the specific system design. Since all the tools and technical support used in the system design process are all free, there is no need for any cost. The design of the system can be done. All the resources used are free, and can be downloaded and used as long as there is a network, and no corresponding fees are required. Therefore, the project is completely feasible in terms of economy.

3.1.3 Operation Feasibility

  I am a student myself, and I have little experience in program development. The interface design should not be too complicated. It should be simple and beautiful, and the operation should be convenient, so that users cannot feel unsmooth. Once the user enters the operation interface, there will be a corresponding prompt on the interface, and the corresponding functional operation module can be found by following the operation prompt, which can be used without training for the user.

  From the feasibility analysis of the above several parts, it can be concluded that the dormitory management system developed this time has no major problems in the development, and it is worth developing.

the code

package com.xyf.resolver;

import java.io.IOException;

import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.springframework.stereotype.Component;
import org.springframework.web.servlet.HandlerExceptionResolver;
import org.springframework.web.servlet.ModelAndView;

import com.xyf.utils.AjaxResult;
import com.xyf.utils.JsonUtils;

/**
 *
 * @author 徐塬峰
 */
@Component
public class XyfHandlerExceptionResolver implements HandlerExceptionResolver {
    
    
    private static final Logger logger = LogManager.getLogger(XyfHandlerExceptionResolver.class);

    @Override
    public ModelAndView resolveException(HttpServletRequest request, HttpServletResponse response, Object handler,
            Exception ex) {
    
    

        logger.error("服务器出错了!", ex);

        //如果是ajax请求,就返回�?个json格式的出错提示信�?
        if (request.getHeader("X-Requested-With") != null) {
    
    
            try {
    
    
                response.getWriter().println(JsonUtils.toJson(AjaxResult.errorInstance("服务器出错了")));
            } catch (IOException e) {
    
    
                logger.error("服务器响应失败", e);
            }
            //返回�?个空的ModelAndView表示已经手动生成响应
            //return null表示使用默认的处理方式,等于没处�?
            return new ModelAndView();
        } else {
    
    
            return new ModelAndView("500");
        }
    }
}

/*
 Navicat Premium Data Transfer

 Source Server         : mysql
 Source Server Type    : MySQL
 Source Server Version : 80027
 Source Host           : localhost:3306
 Source Schema         : ssmbuild

 Target Server Type    : MySQL
 Target Server Version : 80027
 File Encoding         : 65001

 Date: 09/06/2023 12:21:28
*/

SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;

-- ----------------------------
-- Table structure for competition
-- ----------------------------
DROP TABLE IF EXISTS `competition`;
CREATE TABLE `competition`  (
  `competition_id` int NOT NULL,
  `competition_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `competition_description` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `publication_date` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `submission_deadline` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `sponsor` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `venue` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`competition_id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Records of competition
-- ----------------------------
INSERT INTO `competition` VALUES (1, '计算机竞赛', '计算机', '2023-5-25', '2023-5-30', '学校', '机房');
INSERT INTO `competition` VALUES (2, 'Competition 2', 'Description 2', '2023-05-30', '2023-06-30', 'Sponsor 2', 'Venue 2');
INSERT INTO `competition` VALUES (3, 'Competition 3', 'Description 3', '2023-05-30', '2023-06-30', 'Sponsor 3', 'Venue 3');
INSERT INTO `competition` VALUES (4, 'Competition 4', 'Description 4', '2023-05-30', '2023-06-30', 'Sponsor 4', 'Venue 4');
INSERT INTO `competition` VALUES (5, 'Competition 5', 'Description 5', '2023-05-30', '2023-06-30', 'Sponsor 5', 'Venue 5');
INSERT INTO `competition` VALUES (6, 'Competition 6', 'Description 6', '2023-05-30', '2023-06-30', 'Sponsor 6', 'Venue 6');
INSERT INTO `competition` VALUES (7, 'Competition 7', 'Description 7', '2023-05-30', '2023-06-30', 'Sponsor 7', 'Venue 7');
INSERT INTO `competition` VALUES (8, 'Competition 8', 'Description 8', '2023-05-30', '2023-06-30', 'Sponsor 8', 'Venue 8');
INSERT INTO `competition` VALUES (9, 'Competition 9', 'Description 9', '2023-05-30', '2023-06-30', 'Sponsor 9', 'Venue 9');
INSERT INTO `competition` VALUES (10, 'Competition 10', 'Description 10', '2023-05-30', '2023-06-30', 'Sponsor 10', 'Venue 10');
INSERT INTO `competition` VALUES (11, 'Competition 11', 'Description 11', '2023-05-30', '2023-06-30', 'Sponsor 11', 'Venue 11');
INSERT INTO `competition` VALUES (12, 'Competition 12', 'Description 12', '2023-05-30', '2023-06-30', 'Sponsor 12', 'Venue 12');
INSERT INTO `competition` VALUES (13, 'Competition 13', 'Description 13', '2023-05-30', '2023-06-30', 'Sponsor 13', 'Venue 13');
INSERT INTO `competition` VALUES (14, 'Competition 14', 'Description 14', '2023-05-30', '2023-06-30', 'Sponsor 14', 'Venue 14');
INSERT INTO `competition` VALUES (15, 'Competition 15', 'Description 15', '2023-05-30', '2023-06-30', 'Sponsor 15', 'Venue 15');
INSERT INTO `competition` VALUES (16, 'Competition 16', 'Description 16', '2023-05-30', '2023-06-30', 'Sponsor 16', 'Venue 16');
INSERT INTO `competition` VALUES (17, 'Competition 17', 'Description 17', '2023-05-30', '2023-06-30', 'Sponsor 17', 'Venue 17');
INSERT INTO `competition` VALUES (18, 'Competition 18', 'Description 18', '2023-05-30', '2023-06-30', 'Sponsor 18', 'Venue 18');
INSERT INTO `competition` VALUES (19, 'Competition 19', 'Description 19', '2023-05-30', '2023-06-30', 'Sponsor 19', 'Venue 19');
INSERT INTO `competition` VALUES (20, 'Competition 20', 'Description 20', '2023-05-30', '2023-06-30', 'Sponsor 20', 'Venue 20');
INSERT INTO `competition` VALUES (21, 'Competition 21', 'Description 21', '2023-05-30', '2023-06-30', 'Sponsor 21', 'Venue 21');
INSERT INTO `competition` VALUES (22, 'Competition 22', 'Description 22', '2023-05-30', '2023-06-30', 'Sponsor 22', 'Venue 22');
INSERT INTO `competition` VALUES (23, 'Competition 23', 'Description 23', '2023-05-30', '2023-06-30', 'Sponsor 23', 'Venue 23');
INSERT INTO `competition` VALUES (24, 'Competition 24', 'Description 24', '2023-05-30', '2023-06-30', 'Sponsor 24', 'Venue 24');
INSERT INTO `competition` VALUES (25, 'Competition 25', 'Description 25', '2023-05-30', '2023-06-30', 'Sponsor 25', 'Venue 25');
INSERT INTO `competition` VALUES (26, 'Competition 26', 'Description 26', '2023-05-30', '2023-06-30', 'Sponsor 26', 'Venue 26');
INSERT INTO `competition` VALUES (27, 'Competition 27', 'Description 27', '2023-05-30', '2023-06-30', 'Sponsor 27', 'Venue 27');
INSERT INTO `competition` VALUES (28, 'Competition 28', 'Description 28', '2023-05-30', '2023-06-30', 'Sponsor 28', 'Venue 28');
INSERT INTO `competition` VALUES (29, 'Competition 29', 'Description 29', '2023-05-30', '2023-06-30', 'Sponsor 29', 'Venue 29');
INSERT INTO `competition` VALUES (30, 'Competition 30', 'Description 30', '2023-05-30', '2023-06-30', 'Sponsor 30', 'Venue 30');
INSERT INTO `competition` VALUES (31, 'Competition 31', 'Description 31', '2023-05-30', '2023-06-30', 'Sponsor 31', 'Venue 31');
INSERT INTO `competition` VALUES (32, 'Competition 32', 'Description 32', '2023-05-30', '2023-06-30', 'Sponsor 32', 'Venue 32');
INSERT INTO `competition` VALUES (33, 'Competition 33', 'Description 33', '2023-05-30', '2023-06-30', 'Sponsor 33', 'Venue 33');
INSERT INTO `competition` VALUES (34, 'Competition 34', 'Description 34', '2023-05-30', '2023-06-30', 'Sponsor 34', 'Venue 34');
INSERT INTO `competition` VALUES (35, 'Competition 35', 'Description 35', '2023-05-30', '2023-06-30', 'Sponsor 35', 'Venue 35');
INSERT INTO `competition` VALUES (36, 'Competition 36', 'Description 36', '2023-05-30', '2023-06-30', 'Sponsor 36', 'Venue 36');
INSERT INTO `competition` VALUES (37, 'Competition 37', 'Description 37', '2023-05-30', '2023-06-30', 'Sponsor 37', 'Venue 37');
INSERT INTO `competition` VALUES (38, 'Competition 38', 'Description 38', '2023-05-30', '2023-06-30', 'Sponsor 38', 'Venue 38');
INSERT INTO `competition` VALUES (39, 'Competition 39', 'Description 39', '2023-05-30', '2023-06-30', 'Sponsor 39', 'Venue 39');
INSERT INTO `competition` VALUES (40, 'Competition 40', 'Description 40', '2023-05-30', '2023-06-30', 'Sponsor 40', 'Venue 40');
INSERT INTO `competition` VALUES (41, 'Competition 41', 'Description 41', '2023-05-30', '2023-06-30', 'Sponsor 41', 'Venue 41');
INSERT INTO `competition` VALUES (42, 'Competition 42', 'Description 42', '2023-05-30', '2023-06-30', 'Sponsor 42', 'Venue 42');
INSERT INTO `competition` VALUES (43, 'Competition 43', 'Description 43', '2023-05-30', '2023-06-30', 'Sponsor 43', 'Venue 43');
INSERT INTO `competition` VALUES (44, 'Competition 44', 'Description 44', '2023-05-30', '2023-06-30', 'Sponsor 44', 'Venue 44');
INSERT INTO `competition` VALUES (45, 'Competition 45', 'Description 45', '2023-05-30', '2023-06-30', 'Sponsor 45', 'Venue 45');
INSERT INTO `competition` VALUES (46, 'Competition 46', 'Description 46', '2023-05-30', '2023-06-30', 'Sponsor 46', 'Venue 46');
INSERT INTO `competition` VALUES (47, 'Competition 47', 'Description 47', '2023-05-30', '2023-06-30', 'Sponsor 47', 'Venue 47');
INSERT INTO `competition` VALUES (48, 'Competition 48', 'Description 48', '2023-05-30', '2023-06-30', 'Sponsor 48', 'Venue 48');
INSERT INTO `competition` VALUES (49, 'Competition 49', 'Description 49', '2023-05-30', '2023-06-30', 'Sponsor 49', 'Venue 49');
INSERT INTO `competition` VALUES (50, 'Competition 50', 'Description 50', '2023-05-30', '2023-06-30', 'Sponsor 50', 'Venue 50');
INSERT INTO `competition` VALUES (51, 'Competition 51', 'Description 51', '2023-05-30', '2023-06-30', 'Sponsor 51', 'Venue 51');
INSERT INTO `competition` VALUES (52, 'Competition 52', 'Description 52', '2023-05-30', '2023-06-30', 'Sponsor 52', 'Venue 52');
INSERT INTO `competition` VALUES (53, 'Competition 53', 'Description 53', '2023-05-30', '2023-06-30', 'Sponsor 53', 'Venue 53');
INSERT INTO `competition` VALUES (54, 'Competition 54', 'Description 54', '2023-05-30', '2023-06-30', 'Sponsor 54', 'Venue 54');
INSERT INTO `competition` VALUES (55, 'Competition 55', 'Description 55', '2023-05-30', '2023-06-30', 'Sponsor 55', 'Venue 55');
INSERT INTO `competition` VALUES (56, 'Competition 56', 'Description 56', '2023-05-30', '2023-06-30', 'Sponsor 56', 'Venue 56');
INSERT INTO `competition` VALUES (57, 'Competition 57', 'Description 57', '2023-05-30', '2023-06-30', 'Sponsor 57', 'Venue 57');
INSERT INTO `competition` VALUES (58, 'Competition 58', 'Description 58', '2023-05-30', '2023-06-30', 'Sponsor 58', 'Venue 58');
INSERT INTO `competition` VALUES (59, 'Competition 59', 'Description 59', '2023-05-30', '2023-06-30', 'Sponsor 59', 'Venue 59');
INSERT INTO `competition` VALUES (60, 'Competition 60', 'Description 60', '2023-05-30', '2023-06-30', 'Sponsor 60', 'Venue 60');
INSERT INTO `competition` VALUES (61, 'Competition 61', 'Description 61', '2023-05-30', '2023-06-30', 'Sponsor 61', 'Venue 61');
INSERT INTO `competition` VALUES (62, 'Competition 62', 'Description 62', '2023-05-30', '2023-06-30', 'Sponsor 62', 'Venue 62');
INSERT INTO `competition` VALUES (63, 'Competition 63', 'Description 63', '2023-05-30', '2023-06-30', 'Sponsor 63', 'Venue 63');
INSERT INTO `competition` VALUES (64, 'Competition 64', 'Description 64', '2023-05-30', '2023-06-30', 'Sponsor 64', 'Venue 64');
INSERT INTO `competition` VALUES (65, 'Competition 65', 'Description 65', '2023-05-30', '2023-06-30', 'Sponsor 65', 'Venue 65');
INSERT INTO `competition` VALUES (66, 'Competition 66', 'Description 66', '2023-05-30', '2023-06-30', 'Sponsor 66', 'Venue 66');
INSERT INTO `competition` VALUES (67, 'Competition 67', 'Description 67', '2023-05-30', '2023-06-30', 'Sponsor 67', 'Venue 67');
INSERT INTO `competition` VALUES (68, 'Competition 68', 'Description 68', '2023-05-30', '2023-06-30', 'Sponsor 68', 'Venue 68');
INSERT INTO `competition` VALUES (69, 'Competition 69', 'Description 69', '2023-05-30', '2023-06-30', 'Sponsor 69', 'Venue 69');
INSERT INTO `competition` VALUES (70, 'Competition 70', 'Description 70', '2023-05-30', '2023-06-30', 'Sponsor 70', 'Venue 70');
INSERT INTO `competition` VALUES (71, 'Competition 71', 'Description 71', '2023-05-30', '2023-06-30', 'Sponsor 71', 'Venue 71');
INSERT INTO `competition` VALUES (72, 'Competition 72', 'Description 72', '2023-05-30', '2023-06-30', 'Sponsor 72', 'Venue 72');
INSERT INTO `competition` VALUES (73, 'Competition 73', 'Description 73', '2023-05-30', '2023-06-30', 'Sponsor 73', 'Venue 73');
INSERT INTO `competition` VALUES (74, 'Competition 74', 'Description 74', '2023-05-30', '2023-06-30', 'Sponsor 74', 'Venue 74');
INSERT INTO `competition` VALUES (75, 'Competition 75', 'Description 75', '2023-05-30', '2023-06-30', 'Sponsor 75', 'Venue 75');
INSERT INTO `competition` VALUES (76, 'Competition 76', 'Description 76', '2023-05-30', '2023-06-30', 'Sponsor 76', 'Venue 76');
INSERT INTO `competition` VALUES (77, 'Competition 77', 'Description 77', '2023-05-30', '2023-06-30', 'Sponsor 77', 'Venue 77');
INSERT INTO `competition` VALUES (78, 'Competition 78', 'Description 78', '2023-05-30', '2023-06-30', 'Sponsor 78', 'Venue 78');
INSERT INTO `competition` VALUES (79, 'Competition 79', 'Description 79', '2023-05-30', '2023-06-30', 'Sponsor 79', 'Venue 79');
INSERT INTO `competition` VALUES (80, 'Competition 80', 'Description 80', '2023-05-30', '2023-06-30', 'Sponsor 80', 'Venue 80');
INSERT INTO `competition` VALUES (81, 'Competition 81', 'Description 81', '2023-05-30', '2023-06-30', 'Sponsor 81', 'Venue 81');
INSERT INTO `competition` VALUES (82, 'Competition 82', 'Description 82', '2023-05-30', '2023-06-30', 'Sponsor 82', 'Venue 82');
INSERT INTO `competition` VALUES (83, 'Competition 83', 'Description 83', '2023-05-30', '2023-06-30', 'Sponsor 83', 'Venue 83');
INSERT INTO `competition` VALUES (84, 'Competition 84', 'Description 84', '2023-05-30', '2023-06-30', 'Sponsor 84', 'Venue 84');
INSERT INTO `competition` VALUES (85, 'Competition 85', 'Description 85', '2023-05-30', '2023-06-30', 'Sponsor 85', 'Venue 85');
INSERT INTO `competition` VALUES (86, 'Competition 86', 'Description 86', '2023-05-30', '2023-06-30', 'Sponsor 86', 'Venue 86');
INSERT INTO `competition` VALUES (87, 'Competition 87', 'Description 87', '2023-05-30', '2023-06-30', 'Sponsor 87', 'Venue 87');
INSERT INTO `competition` VALUES (88, 'Competition 88', 'Description 88', '2023-05-30', '2023-06-30', 'Sponsor 88', 'Venue 88');
INSERT INTO `competition` VALUES (89, 'Competition 89', 'Description 89', '2023-05-30', '2023-06-30', 'Sponsor 89', 'Venue 89');
INSERT INTO `competition` VALUES (90, 'Competition 90', 'Description 90', '2023-05-30', '2023-06-30', 'Sponsor 90', 'Venue 90');
INSERT INTO `competition` VALUES (91, 'Competition 91', 'Description 91', '2023-05-30', '2023-06-30', 'Sponsor 91', 'Venue 91');
INSERT INTO `competition` VALUES (92, 'Competition 92', 'Description 92', '2023-05-30', '2023-06-30', 'Sponsor 92', 'Venue 92');
INSERT INTO `competition` VALUES (93, 'Competition 93', 'Description 93', '2023-05-30', '2023-06-30', 'Sponsor 93', 'Venue 93');
INSERT INTO `competition` VALUES (94, 'Competition 94', 'Description 94', '2023-05-30', '2023-06-30', 'Sponsor 94', 'Venue 94');
INSERT INTO `competition` VALUES (95, 'Competition 95', 'Description 95', '2023-05-30', '2023-06-30', 'Sponsor 95', 'Venue 95');
INSERT INTO `competition` VALUES (96, 'Competition 96', 'Description 96', '2023-05-30', '2023-06-30', 'Sponsor 96', 'Venue 96');
INSERT INTO `competition` VALUES (97, 'Competition 97', 'Description 97', '2023-05-30', '2023-06-30', 'Sponsor 97', 'Venue 97');
INSERT INTO `competition` VALUES (98, 'Competition 98', 'Description 98', '2023-05-30', '2023-06-30', 'Sponsor 98', 'Venue 98');
INSERT INTO `competition` VALUES (99, 'Competition 99', 'Description 99', '2023-05-30', '2023-06-30', 'Sponsor 99', 'Venue 99');
INSERT INTO `competition` VALUES (100, 'Competition 100', 'Description 100', '2023-05-30', '2023-06-30', 'Sponsor 100', 'Venue 100');
INSERT INTO `competition` VALUES (101, 'Competition 101', 'Description 101', '2023-05-30', '2023-06-30', 'Sponsor 101', 'Venue 101');
INSERT INTO `competition` VALUES (102, 'Competition 102', 'Description 102', '2023-05-30', '2023-06-30', 'Sponsor 102', 'Venue 102');
INSERT INTO `competition` VALUES (103, 'Competition 103', 'Description 103', '2023-05-30', '2023-06-30', 'Sponsor 103', 'Venue 103');
INSERT INTO `competition` VALUES (104, 'Competition 104', 'Description 104', '2023-05-30', '2023-06-30', 'Sponsor 104', 'Venue 104');
INSERT INTO `competition` VALUES (105, 'Competition 105', 'Description 105', '2023-05-30', '2023-06-30', 'Sponsor 105', 'Venue 105');
INSERT INTO `competition` VALUES (106, 'Competition 106', 'Description 106', '2023-05-30', '2023-06-30', 'Sponsor 106', 'Venue 106');
INSERT INTO `competition` VALUES (107, 'Competition 107', 'Description 107', '2023-05-30', '2023-06-30', 'Sponsor 107', 'Venue 107');
INSERT INTO `competition` VALUES (108, 'Competition 108', 'Description 108', '2023-05-30', '2023-06-30', 'Sponsor 108', 'Venue 108');
INSERT INTO `competition` VALUES (109, 'Competition 109', 'Description 109', '2023-05-30', '2023-06-30', 'Sponsor 109', 'Venue 109');
INSERT INTO `competition` VALUES (110, 'Competition 110', 'Description 110', '2023-05-30', '2023-06-30', 'Sponsor 110', 'Venue 110');
INSERT INTO `competition` VALUES (111, 'Competition 111', 'Description 111', '2023-05-30', '2023-06-30', 'Sponsor 111', 'Venue 111');

SET FOREIGN_KEY_CHECKS = 1;

Summarize

  The administrator can manage the information of students and dormitory management in this system, as well as manage buildings, dormitories, and occupancy. Students can view the students and dormitories in this system, but they do not have permission to modify, add, or delete. The dormitory management can log in to this system to manage the dormitory, occupancy, students and other information of the system.

Guess you like

Origin blog.csdn.net/2301_78335941/article/details/131142551
Recommended