Table of contents
1.1Purpose and significance of the topic
1.2Research status at home and abroad
1.3Thesis structure and chapter arrangement
1.4Introduction to the applet framework and directory structure
2Springboot Fishing Dating Platform Mini ProgramSystem Analysis
2.1.1 Technical Feasibility Analysis
2.1.2 Economic Feasibility Analysis
2.1.3 Operation Feasibility Analysis
2.2.1 Several stationary process
2.3.2 Ineffectiveness analysis
3 Springboot Fishing Dating Platform Mini ProgramOverall Design
3.1 System function module design
3.1.1Overall functional module design
3.1.3 Comment management module design
3.1.4Mall management module design
3.1.5Order management module design
3.2.1 Database conceptual structure design
3.2.2 Database logical structure design
4Springboot fishing dating platform appletDetailed design and implementation
4.1.1 Previous stage interface
4.1.4Consumption land interface
4.1.5 Silver point information interface
4.1.6 Product displayInterface
4.2Management staff function model
4.2.1 NotificationManagement interface< /span>
4.2.2 Market centerManagement interface
With the rapid development of our country's economy, people's demand for mobile phones is increasing, and various mobile phone software are also widely used. However, for data information management on mobile phones, various software for mobile phones are also very popular among users. WeChat The fishing dating platform of the mini program is widely used by users. For the convenience of users, the data information management of the fishing dating platform of the WeChat mini program can be carried out at any time. In actual application, the working rules and development steps of the application software are used to build the fishing dating platform applet using Springboot technology.
This design mainly implements a fishing dating platform applet that combines the advantages of humanization, high efficiency and convenience, and completes functional modules such as fishing spot information, weather forecast, article information, contacting fishing friends, and mall management. The system communicates with the server through the browser to realize data interaction and changes. This system improves work efficiency and reduces errors and omissions in data storage through scientific management methods and convenient services. The development project of this Springboot fishing dating platform applet is based on the Springboot framework, adopts the JavaWeb development method, and uses the MySQL database to explain the various functions of the Springboot fishing dating platform applet and the user's needs, and then make friends based on the user's fishing needs, and then introduces the overall design of the system and its detailed design, providing users with a method to build the overall structure of the Springboot fishing dating platform applet. Thereby meeting the needs of users for independent transactions.
Keywords: Springboot; MYSQL; fishing dating platform applet
Abstract
With the rapid development of China's economy, people's demand for mobile phones is increasing, and various mobile phone software are also widely used. But for mobile phone data information management, various software for mobile phones are also popular with users. The phishing and dating platform of WeChat applets is widely used by users. In order to facilitate users to manage the data information of the phishing and dating platform of WeChat applets at any time. In practical application, the working rules and development steps of the application software use Springboot technology to build a small program of the fishing and dating platform.
This design mainly realizes the small program of fishing and dating platform which integrates the advantages of humanization, efficiency and convenience, and completes the functional modules of fishing point information, weather forecast, article information, contact with fishing friends, shopping mall management, etc. The system communicates with the server through the browser to realize data interaction and change. The system improves work efficiency and reduces errors and omissions in data storage through scientific management and convenient services. The development project of this Springboot phishing and dating platform applet is based on the Springboot framework, adopts the development method of Java Web, and uses MySQL database to explain the various functions of this Springboot phishing and dating platform applet and the user's needs, and then introduces the overall design and detailed design of the system according to the user's needs for phishing and dating, It provides users with the construction method of the overall structure of the Springboot fishing and dating platform applet. So as to meet the needs of users' independent trading.
Keywords: Springboot; MYSQL; Fishing and dating platform applet
1 Read
1.1 Purpose and significance of the topic
With the vigorous development and widespread popularization of computer technology and network communication technology, computer networks have become one of the important ways for people to transmit information. And with the popularization and development of smartphones and 4G and 5G networks, mini program application technology is an important aspect of network application technology. It has the advantages of timely communication, fast retrieval, easy use, no memory consumption, and wide application. Mini program technology is also gradually changing people’s lifestyles. As people's lives become more and more colorful, like-minded enthusiasts also have dedicated platforms to communicate. Fishing socialization has actually been a popular lifestyle habit for a long time. Fishing friends can no longer be satisfied with their own leisurely life and gradually form an exclusive social circle. The development and design of a fishing dating platform provides fishing friends with a unique social platform where they can share fishing catches and their own fishing experience on a daily basis to enhance the fun of fishing friends' daily lives. Therefore, the design of the fishing dating platform applet is very necessary. In this way, more and more people can obtain fishing news, fishing spot information, contact with fishing friends and other information through the mini program.
1.2 Research status at home and abroad
There are currently a large number of communication and dating software, systems and websites at home and abroad, and they are diverse. However, due to the wide range of coverage and the different levels of development in each city, they are more based on traditional applications. Personal social networks such as WeChat groups, QQ groups, etc. are used to communicate, and people's energy and work accuracy are limited, so traditional communication methods inevitably have shortcomings such as low efficiency and low accuracy, and are also accompanied by human resources and A huge waste of time. In management work, computer machines are better at the tasks involved than humans and can meet requirements such as speed, accuracy, and low resource consumption. Based on these significant advantages, if a complete fishing dating platform applet can be designed that meets the needs of fishing enthusiasts, it will greatly improve the efficiency of finding like-minded fishing friends and make it easier to make various preparations before traveling. With such a small program, only a small number of personnel are needed to conduct daily data review, management and regular maintenance of the database. During the entire process, managers only need to provide a small amount of necessary information, and most of the data processing work is completed by the database and related programs, saving a lot of time. If there are errors in some part of the information in the database, managers can reduce the time and energy spent in troubleshooting through batch modifications. Therefore, it is very necessary to develop an easy-to-use fishing dating platform applet.
1.3 Paper structure and chapter arrangement
This Springboot fishing dating platform applet is divided into six chapters for introduction. The content of the chapters is arranged as follows:
Chapter 1: Introduction. The first chapter mainly introduces the background of the research on the Springboot fishing dating platform applet, the current situation of the Springboot fishing dating platform applet, and the research content and main work of this article.
Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.
Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.
Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.
Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.
Chapter 6: Summary.
1.4 Introduction to the applet framework and directory structure
The entire mini program framework system is divided into two parts:Logic layer andView layer. The goal of the mini program development framework is to allow developers to develop services with native mini program experience in WeChat in the simplest and most efficient way possible. The mini program provides data transmission and event systems between the view layer and the logic layer, and provides its own view layer and logic layer framework, allowing developers to focus on data and logic. At the core of the framework is a reactive data binding system that makes it very simple to keep data in sync with views. If data is modified in the logic layer, corresponding updates will be made in the view layer. The framework provides a set of basic components, which come with WeChat-style styles and special logic. Developers can create powerful WeChat mini programs by combining basic components.
2 Springboot fishing dating platform applet system analysis
2.1 Feasibility analysis
2.1.1 Technical feasibility analysis
After analyzing the real needs of the Springboot Fishing Dating Platform applet, the roles required by the Springboot Fishing Dating Platform applet were divided into Figures 2-1 and 2-2 below.
From the perspective of development tools, since the Springboot fishing dating platform applet is based on JAVA technology, it can be developed with all the development tools currently on the market. These powerful development tools can bring great convenience to me in designing the project. .
Judging from the technology of the Springboot fishing dating platform applet, it is not troublesome for me to develop a Springboot fishing dating platform applet. The development of the Springboot fishing dating platform applet can be simply divided into front-end module development, back-end module development and database development. Most of the technical difficulties have been used when I was in school, and there are many technical points on the Internet that I can learn from. Web background management uses JAVA, springboot and other technologies, and the database uses mysql. Therefore, it saves me a lot of redundant code in developing the Springboot fishing dating platform applet, which brings great convenience to my completion project writing. convenient.
From the perspective of user experience, I can refer to many widely used e-commerce cases on the market such as Taobao. Therefore, I can combine the advantages of page interaction design on Taobao and revise it based on the characteristics of my graduation project. Finally, Achieve a satisfactory page interaction experience for users. To sum up, from a technical perspective, it is feasible to develop the Springboot fishing dating platform applet.
2.1.2 Economic feasibility analysis
Judging from the development cost of the Springboot Fishing Dating Platform applet, I completed the design and development of the Springboot Fishing Dating Platform applet myself, and there were no other costs.
Judging from the maintenance cost of the Springboot Fishing Dating Platform applet, the development of the Springboot Fishing Dating Platform applet follows a complete set of code writing specifications, and the structural design of the Springboot Fishing Dating Platform applet is very flexible and follows the high cohesion and low coupling principle. principles, making it easy to maintain and develop iteratively.
After the Springboot Fishing Dating Platform applet is launched, I will investigate based on real needs in the early stage of the launch and develop a set of appropriate usage fees for the Springboot Fishing Dating Platform applet I developed. After the system is stable, I will expand the scope of promotion to other industries. They can register and use my Springboot fishing dating platform applet by themselves. They only need to pay a small deposit, and I will introduce advertising investment and self-operated business to them.
Based on the above analysis, the economic benefits brought by the Springboot fishing dating platform applet will bring great benefits. And with my promotion, the market for using the Springboot Fishing Dating Platform applet I developed will become larger and larger, and the Springboot Fishing Dating Platform applet will bring more and more profits. Therefore, from an economic perspective, it is feasible to develop the Springboot fishing dating platform applet.
2.1.3 Operation feasibility analysis
The Springboot fishing dating platform applet developed this time is relatively simple and can be used by users who can surf the Internet. After entering the system, you can perform corresponding operations according to the prompts. Both the system's operation settings and the system's logical design are relatively simple. , for example, when a user wants to buy a certain fishing gear product, he must first understand the various parameters of the fishing gear product. In the process of understanding, we have set up an eye-catching purchase menu on this page to facilitate the user's purchase, so in It seems to be relatively easy for users to operate; looking at the administrator management part, our system price settings and various parameter settings are fixed. Operators can add, delete, modify and check as long as they enter, which is very convenient. Overall, the system is operationally feasible.
2.2.1 Number of fixed steps
The purpose of the Springboot fishing dating platform applet is to enable the online purchase of fishing gear. Figure 2-1 is the data flow diagram of the system.
Figure 2-1Fishing gearExpanded view of purchase operation
3.3.2 Business process
After analyzing the data flow of the system, let’s look at the business process of the system. Figure 2-2 is the business flow chart:
Figure 2-2 Business flow chart
According to the roles of the Springboot fishing dating platform applet, I divided it into two parts: the user management module and the administrator management module.
User management module:
(1) User registration and login: User registration and login to the Springboot fishing dating platform applet
(2) Mall Center: Users can browse product information, and after discovering products they like, they can add purchases + purchase + comments + collections.
(3) Personal information: Users can modify personal information, avatar, and nickname.
(4) Website announcements: Users read announcement messages and view bank announcement information released by managers.
(5) Shopping cart: Users can add additional purchases to their favorite products. In the shopping cart, they can view all purchased products, support changing the quantity of products, deleting products, and making selections for purchase.
(6) Fishing point information: In the "Fishing point information" column, users can search for fishing point names and tide conditions to view detailed information such as fishing point types, fishing point locations, empty fishing locations, tide conditions, detailed descriptions, etc. View map details, reserve fishing spots, like, comment and other operations;
(7) Weather forecast: Click the "Weather Forecast" column to publish or query the weather conditions of a certain place;
(8) My Collection: When you click the "My Collection" button in "My", various information collected by you will be displayed. Search and query for collection information are supported. If you no longer want to collect a certain information , just click Delete.
(9) My Order: Click "My Order" to view your order information.
(10) Article information: Click the "Article Information" column to view the article information published by the administrator. You can collect, like, comment on your favorite articles, and also publish article information;
(11) Contact fishing friends: In the “Contact Fishing Friends” column, you can edit the contact content and choose to send it to the fishing friends who need to be contacted;
Administrator management module:
(1) System announcement management: The administrator can publish some announcements displayed on the home page of the Springboot fishing dating platform applet to the system, so that users can view system information in a timely manner and make reasonable arrangements.
(2) Carousel image management: The administrator can publish the carousel image displayed on the homepage of the Springboot Fishing Dating Platform applet to the system so that users can view the carousel image information.
(2) User management: Administrators can manage and control all users in the Springboot fishing dating platform applet, including administrators and registered users.
(3) Mall Center: In the background, the administrator can add, delete, modify and check the product information displayed in the Springboot Fishing Dating Platform applet and classify and manage the mall order information.
(4) Module management: The administrator can manage the six sub-menus of confirmed booking + weather forecast + fishing spot information + reserved fishing position + article information + contact fishing friends in the module management of the Springboot fishing dating platform applet in the background.
The non-functional requirements of the Springboot Fishing Dating Platform applet include the security, reliability, performance, scalability, etc. of the Springboot Fishing Dating Platform applet. The details can be expressed in the following 3-1 table:
Table3-1Springboot Fishing Dating Platform Mini ProgramNon-functional requirements list
safety |
Mainly refers to the installation of the Springboot fishing dating platform applet database. The use of the database and the setting of passwords must comply with the standards. |
reliability |
Reliability means that the Springboot fishing dating platform applet can be installed and operated according to the user's instructions. After testing, the reliability is more than 90%. |
performance |
Performance is a necessary condition for the Springboot fishing dating platform applet to occupy the market, so it is best to have good performance. |
Scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
Ease of use |
Users only need to follow the page display content of the Springboot fishing dating platform applet and it will be fine. |
maintainability |
The maintainability of the Springboot fishing dating platform applet development is very important. After testing, there is no problem with the maintainability. |
2.4 Series example analysis
Through the analysis of 2.3 functions, the use case diagram of this Springboot fishing dating platform applet is obtained:
An example of a user role is shown in Figure 2-3.
Figure 2-3 Springboot fishing dating platform applet user role use case diagram
The administrator of the web background management maintains all data information in the entire Springboot fishing dating platform applet. An example of the administrator role is shown in Figure 2-4.
Figure 2-4 Springboot fishing dating platform applet administrator role use case diagram
This chapter mainly determines the functions to be realized by the entire Springboot Fishing Dating Platform applet through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis. At the same time, it also provides standards for code implementation and testing of Springboot fishing dating platform applet.
3 Overall design of Springboot fishing dating platform applet
The main contents discussed in this chapter includeThe functional module design and database system design of the Springboot fishing dating platform applet.
3.1 System function module design
3.1.1 Overall functional module design
In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in this Springboot fishing dating platform applet were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this Springboot fishing dating platform applet. The Springboot fishing dating platform applet is derived based on the demand analysis in the previous chapter. Its overall design module diagram is shown in Figure 3-1.
Figure 3-1 Function module diagram of Springboot fishing dating platform applet
3.1.2 User module design
The backend manager can add, delete, modify and check the users registered in the frontend. The user module structure diagram is as follows:
Figure 3-2 User module structure diagram
3.1.3 Comment management module design
The Springboot Fishing Dating Platform applet is a public platform for communication. Users can communicate on the platform to increase the interactivity between users. But at the same time, in order to better standardize the content of comments and give administrators the function of deleting inappropriate comments, a comment management module needs to be specially designed. The specific structure diagram is as follows:
Figure 3-3 Structure diagram of comment module
3.1.4 Mall management module design
Springboot fishing dating platform applet needs to store a lot of product information. Its module function structure, the specific structure diagram is as follows:
Figure 3-4 Mall module structure diagram
3.1.5 Order Management Module Design
Springboot Fishing Dating Platform Mini ProgramThe most important function is purchase. Its module function structure, the specific structure diagram is as follows:
Figure 3-5 Order module structure diagram
Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.
3.2.1 Database conceptual structure design
The following is the main E-R entity relationship diagram of the main database tables in the entire Springboot fishing dating platform applet.
Figure 3-6 Springboot fishing dating platform applet total E-R relationship diagram
3.2.2 Database logical structure design
From the total E-R relationship diagram in the Springboot fishing dating platform applet in the previous section, it can be concluded that a total of many data tables need to be created. Here I mainly list several major database table structure designs.
Table access_token (login access duration)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
token_id |
int |
10 |
0 |
N |
AND |
Temporary access badge ID |
|
2 |
token |
varchar |
64 |
0 |
AND |
N |
temporary access badge |
|
3 |
info |
text |
65535 |
0 |
AND |
N |
||
4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table address (shipping address:)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
address_id |
int |
10 |
0 |
N |
AND |
Shipping address: |
|
2 |
name |
varchar |
32 |
0 |
AND |
N |
Name: |
|
3 |
phone |
varchar |
13 |
0 |
AND |
N |
cell phone: |
|
4 |
postcode |
varchar |
8 |
0 |
AND |
N |
post code: |
|
5 |
address |
varchar |
255 |
0 |
N |
N |
address: |
|
6 |
user_id |
mediumint |
8 |
0 |
N |
N |
User ID: [0,8388607] User obtains other user-related data |
|
7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
9 |
default |
bit |
1 |
0 |
N |
N |
0 |
Default judgment |
Table article_information (article information)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
article_information_id |
int |
10 |
0 |
N |
AND |
Article information ID |
|
2 |
article_title |
varchar |
64 |
0 |
AND |
N |
Article title |
|
3 |
cover |
varchar |
255 |
0 |
AND |
N |
cover |
|
4 |
photo_1 |
varchar |
255 |
0 |
AND |
N |
Photo 1 |
|
5 |
photo_2 |
varchar |
255 |
0 |
AND |
N |
Photo 2 |
|
6 |
publishing_users |
int |
10 |
0 |
AND |
N |
0 |
publish user |
7 |
experience_content |
text |
65535 |
0 |
AND |
N |
Experience content |
|
8 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
9 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
11 |
location_address |
varchar |
64 |
0 |
AND |
N |
current location |
|
12 |
location_lng |
varchar |
64 |
0 |
AND |
N |
Current location longitude |
|
13 |
location_lat |
varchar |
64 |
0 |
AND |
N |
Current location latitude |
|
14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table auth (user rights management)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
auth_id |
int |
10 |
0 |
N |
AND |
Authorization ID: |
|
2 |
user_group |
varchar |
64 |
0 |
AND |
N |
user group: |
|
3 |
mod_name |
varchar |
64 |
0 |
AND |
N |
Module name: |
|
4 |
table_name |
varchar |
64 |
0 |
AND |
N |
Table Name: |
|
5 |
page_title |
varchar |
255 |
0 |
AND |
N |
page title: |
|
6 |
path |
varchar |
255 |
0 |
AND |
N |
Routing path: |
|
7 |
position |
varchar |
32 |
0 |
AND |
N |
Location: |
|
8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
Jump method: |
9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to add: |
10 |
of the |
tinyint |
3 |
0 |
N |
N |
1 |
Can it be deleted: |
11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
Whether it can be modified: |
12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to view: |
13 |
field_add |
text |
65535 |
0 |
AND |
N |
Add fields: |
|
14 |
field_set |
text |
65535 |
0 |
AND |
N |
Modify fields: |
|
15 |
field_get |
text |
65535 |
0 |
AND |
N |
Query fields: |
|
16 |
table_nav_name |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation name: |
|
17 |
table_nav |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation: |
|
18 |
option |
text |
65535 |
0 |
AND |
N |
Configuration: |
|
19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
table cart (shopping cart)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
cart_id |
int |
10 |
0 |
N |
AND |
Shopping cart ID: |
|
2 |
title |
varchar |
64 |
0 |
AND |
N |
title: |
|
3 |
img |
varchar |
255 |
0 |
N |
N |
0 |
picture: |
4 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID: |
5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
7 |
state |
int |
10 |
0 |
N |
N |
0 |
Status: In use, expired |
8 |
price |
double |
9 |
2 |
N |
N |
0.00 |
unit price: |
9 |
price_ago |
double |
9 |
2 |
N |
N |
0.00 |
Original price: |
10 |
price_count |
double |
11 |
2 |
N |
N |
0.00 |
Total price: |
11 |
on one |
int |
10 |
0 |
N |
N |
1 |
quantity: |
12 |
goods_id |
mediumint |
8 |
0 |
N |
N |
Product id: [0,8388607] |
|
13 |
type |
varchar |
64 |
0 |
N |
N |
uncategorized |
Categories: |
14 |
description |
varchar |
255 |
0 |
AND |
N |
Description: [0,255] is used for product specification description |
table collect (collection)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
collect_id |
int |
10 |
0 |
N |
AND |
Collection ID: |
|
2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Collector ID: |
3 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
4 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
6 |
title |
varchar |
255 |
0 |
AND |
N |
title: |
|
7 |
img |
varchar |
255 |
0 |
AND |
N |
Cover: |
|
8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table comment (comment)
serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
1 |
comment_id |
int |
10 |
0 |
N |
AND |
Comment ID: |
|
2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
评论人ID: |
3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
回复评论ID:空为0 |
4 |
content |
longtext |
2147483647 |
0 |
Y |
N |
内容: |
|
5 |
nickname |
varchar |
255 |
0 |
Y |
N |
昵称: |
|
6 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址:[0,255] |
|
7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
9 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
10 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID: |
表confirm_reservation (确认预定)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
confirm_reservation_id |
int |
10 |
0 |
N |
Y |
确认预定ID |
|
2 |
appointment_no |
varchar |
64 |
0 |
N |
N |
预约号 |
|
3 |
fishing_point_number |
varchar |
64 |
0 |
Y |
N |
钓点编号 |
|
4 |
fishing_point_name |
varchar |
64 |
0 |
Y |
N |
钓点名称 |
|
5 |
cover |
varchar |
255 |
0 |
Y |
N |
封面 |
|
6 |
fishing_point_type |
varchar |
64 |
0 |
Y |
N |
钓点类型 |
|
7 |
tidal_conditions |
varchar |
64 |
0 |
Y |
N |
潮汐情况 |
|
8 |
location |
varchar |
64 |
0 |
Y |
N |
地点位置 |
|
9 |
scheduled_users |
int |
10 |
0 |
Y |
N |
0 |
预定用户 |
10 |
predetermined_number_of_digits |
varchar |
64 |
0 |
Y |
N |
预定位数 |
|
11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表contact_fishing_friends (联系钓友)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
contact_fishing_friends_id |
int |
10 |
0 |
N |
Y |
联系钓友ID |
|
2 |
send_user |
int |
10 |
0 |
Y |
N |
0 |
发送用户 |
3 |
accept_users |
int |
10 |
0 |
Y |
N |
0 |
接受用户 |
4 |
contact_content |
text |
65535 |
0 |
Y |
N |
联系内容 |
|
5 |
send_date |
date |
10 |
0 |
Y |
N |
发送日期 |
|
6 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
7 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表fishing_point_information (钓点信息)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
fishing_point_information_id |
int |
10 |
0 |
N |
Y |
钓点信息ID |
|
2 |
fishing_point_number |
varchar |
64 |
0 |
Y |
N |
钓点编号 |
|
3 |
fishing_point_name |
varchar |
64 |
0 |
Y |
N |
钓点名称 |
|
4 |
cover |
varchar |
255 |
0 |
Y |
N |
封面 |
|
5 |
fishing_point_type |
varchar |
64 |
0 |
Y |
N |
钓点类型 |
|
6 |
tidal_conditions |
varchar |
64 |
0 |
Y |
N |
潮汐情况 |
|
7 |
location |
varchar |
64 |
0 |
Y |
N |
地点位置 |
|
8 |
empty_fishing_number |
int |
10 |
0 |
Y |
N |
0 |
空钓位数 |
9 |
details |
text |
65535 |
0 |
Y |
N |
详情说明 |
|
10 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
12 |
timer_title |
varchar |
64 |
0 |
Y |
N |
计时器标题 |
|
13 |
timing_start_time |
datetime |
19 |
0 |
Y |
N |
计时开始时间 |
|
14 |
timing_end_time |
datetime |
19 |
0 |
Y |
N |
计时结束时间 |
|
15 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
16 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表goods (商品信息)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
goods_id |
mediumint |
8 |
0 |
N |
Y |
产品id:[0,8388607] |
|
2 |
title |
varchar |
125 |
0 |
Y |
N |
标题:[0,125]用于产品和html的<title>标签中 |
|
3 |
img |
text |
65535 |
0 |
Y |
N |
封面图:用于显示于产品列表页 |
|
4 |
description |
varchar |
255 |
0 |
Y |
N |
描述:[0,255]用于产品规格描述 |
|
5 |
price_ago |
double |
8 |
2 |
N |
N |
0.00 |
原价:[1] |
6 |
price |
double |
8 |
2 |
N |
N |
0.00 |
卖价:[1] |
7 |
sales |
int |
10 |
0 |
N |
N |
0 |
销量:[0,1000000000] |
8 |
inventory |
int |
10 |
0 |
N |
N |
0 |
商品库存 |
9 |
type |
varchar |
64 |
0 |
N |
N |
商品分类: |
|
10 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量:[0,1000000000]访问这篇产品的人次 |
11 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文:产品的主体内容 |
|
12 |
img_1 |
text |
65535 |
0 |
Y |
N |
主图1: |
|
13 |
img_2 |
text |
65535 |
0 |
Y |
N |
主图2: |
|
14 |
img_3 |
text |
65535 |
0 |
Y |
N |
主图3: |
|
15 |
img_4 |
text |
65535 |
0 |
Y |
N |
主图4: |
|
16 |
img_5 |
text |
65535 |
0 |
Y |
N |
主图5: |
|
17 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
19 |
customize_field |
text |
65535 |
0 |
Y |
N |
自定义字段 |
|
20 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
21 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
22 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID: |
23 |
user_id |
int |
10 |
0 |
Y |
N |
0 |
添加人 |
表goods_type (商品类型)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
type_id |
int |
10 |
0 |
N |
Y |
商品分类ID: |
|
2 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
上级分类ID:[0,32767] |
3 |
name |
varchar |
255 |
0 |
Y |
N |
商品名称: |
|
4 |
desc |
varchar |
255 |
0 |
Y |
N |
描述: |
|
5 |
icon |
varchar |
255 |
0 |
Y |
N |
图标: |
|
6 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
7 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
表hits (用户点击)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
hits_id |
int |
10 |
0 |
N |
Y |
点赞ID: |
|
2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人: |
3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID: |
表mall_center (商城中心)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
mall_center_id |
int |
10 |
0 |
N |
Y |
商城中心ID |
|
2 |
manufactor |
varchar |
64 |
0 |
Y |
N |
厂家 |
|
3 |
specifications |
varchar |
64 |
0 |
Y |
N |
规格 |
|
4 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
5 |
cart_title |
varchar |
125 |
0 |
Y |
N |
标题:[0,125]用于产品html的标签中 |
|
6 |
cart_img |
text |
65535 |
0 |
Y |
N |
封面图:用于显示于产品列表页 |
|
7 |
cart_description |
varchar |
255 |
0 |
Y |
N |
描述:[0,255]用于产品规格描述 |
|
8 |
cart_price_ago |
double |
8 |
2 |
N |
N |
0.00 |
原价:[1] |
9 |
cart_price |
double |
8 |
2 |
N |
N |
0.00 |
卖价:[1] |
10 |
cart_inventory |
int |
10 |
0 |
N |
N |
0 |
商品库存 |
11 |
cart_type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类: |
12 |
cart_content |
longtext |
2147483647 |
0 |
Y |
N |
正文:产品的主体内容 |
|
13 |
cart_img_1 |
text |
65535 |
0 |
Y |
N |
主图1: |
|
14 |
cart_img_2 |
text |
65535 |
0 |
Y |
N |
主图2: |
|
15 |
cart_img_3 |
text |
65535 |
0 |
Y |
N |
主图3: |
|
16 |
cart_img_4 |
text |
65535 |
0 |
Y |
N |
主图4: |
|
17 |
cart_img_5 |
text |
65535 |
0 |
Y |
N |
主图5: |
|
18 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
19 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表notice (公告)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
公告id: |
|
2 |
title |
varchar |
125 |
0 |
N |
N |
标题: |
|
3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文: |
|
4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
表order (订单)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
order_id |
int |
10 |
0 |
N |
Y |
订单ID: |
|
2 |
order_number |
varchar |
64 |
0 |
Y |
N |
订单号: |
|
3 |
goods_id |
mediumint |
8 |
0 |
N |
N |
商品id:[0,8388607] |
|
4 |
title |
varchar |
32 |
0 |
Y |
N |
商品标题: |
|
5 |
img |
varchar |
255 |
0 |
Y |
N |
商品图片: |
|
6 |
price |
double |
10 |
2 |
N |
N |
0.00 |
价格: |
7 |
price_ago |
double |
10 |
2 |
N |
N |
0.00 |
原价: |
8 |
num |
int |
10 |
0 |
N |
N |
1 |
数量: |
9 |
price_count |
double |
8 |
2 |
N |
N |
0.00 |
总价: |
10 |
norms |
varchar |
255 |
0 |
Y |
N |
规格: |
|
11 |
type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类: |
12 |
contact_name |
varchar |
32 |
0 |
Y |
N |
联系人姓名: |
|
13 |
contact_email |
varchar |
125 |
0 |
Y |
N |
联系人邮箱: |
|
14 |
contact_phone |
varchar |
11 |
0 |
Y |
N |
联系人手机: |
|
15 |
contact_address |
varchar |
255 |
0 |
Y |
N |
收件地址: |
|
16 |
postal_code |
varchar |
9 |
0 |
Y |
N |
邮政编码: |
|
17 |
user_id |
int |
10 |
0 |
N |
N |
0 |
买家ID: |
18 |
merchant_id |
mediumint |
8 |
0 |
N |
N |
0 |
商家ID: |
19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
21 |
description |
varchar |
255 |
0 |
Y |
N |
描述:[0,255]用于产品规格描述 |
|
22 |
state |
varchar |
16 |
0 |
N |
N |
待付款 |
订单状态:待付款,待发货,待签收,已签收,待退款,已退款,已拒绝,已完成 |
表praise (点赞)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
praise_id |
int |
10 |
0 |
N |
Y |
点赞ID: |
|
2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人: |
3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID: |
8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞,0已取消 |
表reservation_of_fishing_position (预定钓位)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
reservation_of_fishing_position_id |
int |
10 |
0 |
N |
Y |
预定钓位ID |
|
2 |
appointment_no |
varchar |
64 |
0 |
Y |
N |
预约号 |
|
3 |
fishing_point_number |
varchar |
64 |
0 |
Y |
N |
钓点编号 |
|
4 |
fishing_point_name |
varchar |
64 |
0 |
Y |
N |
钓点名称 |
|
5 |
cover |
varchar |
255 |
0 |
Y |
N |
封面 |
|
6 |
fishing_point_type |
varchar |
64 |
0 |
Y |
N |
钓点类型 |
|
7 |
tidal_conditions |
varchar |
64 |
0 |
Y |
N |
潮汐情况 |
|
8 |
location |
varchar |
64 |
0 |
Y |
N |
地点位置 |
|
9 |
scheduled_users |
int |
10 |
0 |
Y |
N |
0 |
预定用户 |
10 |
predetermined_number_of_digits |
varchar |
64 |
0 |
Y |
N |
预定位数 |
|
11 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
12 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表slides (轮播图)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID: |
|
2 |
title |
varchar |
64 |
0 |
Y |
N |
标题: |
|
3 |
content |
varchar |
255 |
0 |
Y |
N |
内容: |
|
4 |
url |
varchar |
255 |
0 |
Y |
N |
链接: |
|
5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图: |
|
6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量: |
7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
表system_user (系统用户)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
system_user_id |
int |
10 |
0 |
N |
Y |
系统用户ID |
|
2 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
3 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
4 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
6 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表upload (文件上传)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
表user (用户账户:用于保存用户登录信息)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
用户ID:[0,8388607]用户获取其他与用户相关的数据 |
|
2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
账户状态:[0,10](1可用|2异常|3已冻结|4已注销) |
3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组:[0,32767]决定用户身份和权限 |
|
4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间: |
5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码:[0,11]用户的手机号码,用于找回密码时或登录时 |
|
6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证:[0,1](0未认证|1审核中|2已认证) |
7 |
username |
varchar |
16 |
0 |
N |
N |
用户名:[0,16]用户登录时所用的账户名称 |
|
8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称:[0,16] |
|
9 |
password |
varchar |
64 |
0 |
N |
N |
密码:[0,32]用户登录所需的密码,由6-16位数字或英文组成 |
|
10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱:[0,64]用户的邮箱,用于找回密码时或登录时 |
|
11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证:[0,1](0未认证|1审核中|2已认证) |
12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址:[0,255] |
|
13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
表user_group (用户组:用于用户前端身份和鉴权)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID:[0,8388607] |
|
2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序:[0,1000] |
3 |
name |
varchar |
16 |
0 |
N |
N |
名称:[0,16] |
|
4 |
description |
varchar |
255 |
0 |
Y |
N |
描述:[0,255]描述该用户组的特点或权限范围 |
|
5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表: |
|
6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段: |
|
7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID: |
8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间: |
10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间: |
表weather_forecast (天气预报)
编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
1 |
weather_forecast_id |
int |
10 |
0 |
N |
Y |
天气预报ID |
|
2 |
title |
varchar |
64 |
0 |
Y |
N |
标题 |
|
3 |
cover |
varchar |
255 |
0 |
Y |
N |
封面 |
|
4 |
air_temperature |
int |
10 |
0 |
Y |
N |
0 |
气温 |
5 |
weather_condition |
varchar |
64 |
0 |
Y |
N |
天气情况 |
|
6 |
description |
text |
65535 |
0 |
Y |
N |
情况说明 |
|
7 |
publishing_users |
int |
10 |
0 |
Y |
N |
0 |
发布用户 |
8 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
10 |
timer_title |
varchar |
64 |
0 |
Y |
N |
计时器标题 |
|
11 |
timing_start_time |
datetime |
19 |
0 |
Y |
N |
计时开始时间 |
|
12 |
timing_end_time |
datetime |
19 |
0 |
Y |
N |
计时结束时间 |
|
13 |
location_address |
varchar |
64 |
0 |
Y |
N |
当前位置 |
|
14 |
location_lng |
varchar |
64 |
0 |
Y |
N |
当前位置经度 |
|
15 |
location_lat |
varchar |
64 |
0 |
Y |
N |
当前位置纬度 |
|
16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
17 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
3.4本章小结
整个Springboot钓鱼交友平台小程序的需求分析主要对系统总体架构以及功能模块的设计,通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 Springboot钓鱼交友平台小程序详细设计与实现
Springboot钓鱼交友平台小程序的详细设计与实现主要是根据前面的Springboot钓鱼交友平台小程序的需求分析和Springboot钓鱼交友平台小程序的总体设计来设计页面并实现业务逻辑。主要从Springboot钓鱼交友平台小程序界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 前台首页界面
当进入Springboot钓鱼交友平台小程序的时候,首先映入眼帘的是系统的导航栏,下面是轮播图以及系统内容,其主界面展示如下图4-1所示。
图4-1 前台首页界面图
4.1.2 用户注册界面
普通的用户只支持对首页部分内容的浏览,想要购买或者查看搜索商品就必须登录到系统,如果你没有本Springboot钓鱼交友平台小程序的账号的话,添加“注册”根据提示输入好用户信息后,点击“注册”按钮后,系统会对输入的信息进行验证,验证输入的账户名和数据库表中已经注册的账户名是否重复,只有都验证没问题后即可用户注册成功。其用用户注册界面展示如下图4-2所示。
图4-2 前台用户注册界面图
4.1.3 用户登录界面
Springboot钓鱼交友平台小程序中的前台上注册后的用户是可以通过自己的账户名和密码进行登录的,当用户输入完整的自己的账户名和密码信息并点击“登录”按钮后,将会首先验证输入的有没有空数据,再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致,只有在一致后将会登录成功并自动跳转到Springboot钓鱼交友平台小程序的首页中;否则将会提示相应错误信息,用户登录界面如下图4-3所示。
图4-3用户登录界面图
用户登录的关键代码如下。
/**
* 登录
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {
log.info("[执行登录接口]");
String username = data.get("username");
String email = data.get("email");
String phone = data.get("phone");
String password = data.get("password");
List resultList = null;
Map<String, String> map = new HashMap<>();
if(username != null && "".equals(username) == false){
map.put("username", username);
resultList = service.select(map, new HashMap<>()).getResultList();
}
else if(email != null && "".equals(email) == false){
map.put("email", email);
resultList = service.select(map, new HashMap<>()).getResultList();
}
else if(phone != null && "".equals(phone) == false){
map.put("phone", phone);
resultList = service.select(map, new HashMap<>()).getResultList();
}else{
return error(30000, "账号或密码不能为空");
}
if (resultList == null || password == null) {
return error(30000, "账号或密码不能为空");
}
//判断是否有这个用户
if (resultList.size()<=0){
return error(30000,"用户不存在");
}
User byUsername = (User) resultList.get(0);
4.1.4收货地址界面
当用户点击“收货地址”右后,就回去显示出目前现有的地址,也可以添加新的地址,收货地址界面如下图4-4所示。
图4-4收货地址界面图
收货地址的关键代码如下。
@PostMapping("/add")
@Transactional
public Map<String, Object> add(HttpServletRequest request) throws IOException {
service.insert(service.readBody(request.getReader()));
return success(1);
}
@Transactional
public Map<String, Object> addMap(Map<String,Object> map){
service.insert(map);
return success(1);
}
4.1.5 钓点信息界面
当用户点击“钓点信息”后,可通过搜索钓点名称和潮汐情况进行查看钓点类型、钓点位置、空钓位置、潮汐情况、详情说明等详细信息,可查看地图详情、预定钓位、点赞、评论等操作;界面如下图4-5所示。
图4-5钓点信息界面图
4.1.6 产品展示界面
当访客点击了任意商品后将会进入该款商品的详情界面,可以了解到该商品的图片信息、商品描述、价钱等,同时可以对该商品进行加购+立即购买+收藏+点赞+评论,产品展示展示页面如图4-6所示。
图4-6 产品展示界面图
产品展示的关键代码如下。
@RequestMapping(value = {"/count_group", "/count"})
public Map<String, Object> count(HttpServletRequest request) {
Query count = service.count(service.readQuery(request), service.readConfig(request));
return success(count.getResultList());
}
4.1.7 我的订单界面
当用户点击“我的订单”链接后就进入自己购买的订单的界面展示,界面如下图4-7所示。
图4-7 我的订单界面图
我的订单的关键代码:
@RequestMapping("/get_list")
public Map<String, Object> getList(HttpServletRequest request) {
Map<String, Object> map = service.selectToPage(service.readQuery(request), service.readConfig(request));
return success(map);
}
点击“文章信息”栏,可查看管理员发布的文章信息,对喜欢的文章可以收藏、点赞、发表评论,也可发布文章信息;界面如下图4-8所示。
图4-7 文章信息界面图
4.1.9联系钓友界面
在“联系钓友”一栏可编辑联系内容选择要发送到需要联系的钓友;界面如下图4-9所示。
图4-9 联系钓友面图
4.2管理员功能模块
4.2.1 公告管理界面
管理员可以对Springboot钓鱼交友平台小程序中的公告信息进行增删改查操作。界面如下图4-10所示。
图4-10 公告管理界面图
管理员在后台可以对Springboot钓鱼交友平台小程序中显示的商城中心及其商品信息进行增删改查,界面如下图4-11所示。
图4-11商城中心管理界面图
商城中心管理关键代码:
@RequestMapping(value = {"/avg_group", "/avg"})
public Map<String, Object> avg(HttpServletRequest request) {
Query count = service.avg(service.readQuery(request), service.readConfig(request));
return success(count.getResultList());
}
4.2.3 订单列表管理界面
管理员可以对Springboot钓鱼交友平台小程序中的订单信息进行维护管理。界面如下图4-12所示。
图4-12订单列表管理界面图
订单列表管理的关键代码如下。
@RequestMapping("/get_obj")
public Map<String, Object> obj(HttpServletRequest request) {
Query select = service.select(service.readQuery(request), service.readConfig(request));
List resultList = select.getResultList();
if (resultList.size() > 0) {
JSONObject jsonObject = new JSONObject();
jsonObject.put("obj",resultList.get(0));
return success(jsonObject);
} else {
return success(null);
}
}
public Query select(Map<String,String> query,Map<String,String> config){
StringBuffer sql = new StringBuffer("select ");
sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");
sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));
if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){
sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");
}
if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){
sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");
}
if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){
int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;
int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;
sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);
}
log.info("[{}] - 查询操作,sql: {}",table,sql);
return runEntitySql(sql.toString());
}
5系统测试
系统的前台、后台、数据库完成以后,这个系统才算是完成了一半,我们在这之后要对系统进行最后的一个阶段,那就是测试了,测试对一个系统来说是非常重要的,有的时候开发完一个系统,如果测试不合格的话,这个系统是没有办法进行投入使用的,所有我们要用测试对系统的功能进行检验,把不完善的功能尽量完善,把出现的bug解决掉,然后给用户呈现出一个完美的系统。通过对系统最后一步的测试,使得开发人员对自己的系统更加有信心,更加积极的为后期的系统版本的更新提供支持。
系统测试包括:用户登录功能测试、商品展示功能测试、商品搜索、密码修改功能测试,如表5-1、5-2、5-3、5-4所示:
表5-1 用户登录功能测试表
商品查看功能测试:
表5-2 商品查看功能测试表
商品搜索功能测试:
表5-3商品搜索功能测试表
密码修改功能测试:
表5-4 密码修改功能测试表
通过编写Springboot钓鱼交友平台小程序的测试用例,已经检测完毕用户登录模块、商品查看模块、商品购买模块、密码修改功能测试,通过这4大模块为Springboot钓鱼交友平台小程序的后期推广运营提供了强力的技术支撑。
至此论文结束,感谢您的阅读。在此我要感谢我的导师,虽然我在实习期间很忙,论文撰写总是停停改改,但是导师依然十分负责,时不时的询问我的任务进展情况,跟进我的论文进度。虽然我在实习期间很忙,以至于很晚才开始进行论文撰写和编写程序的工作,但是在指导老师的帮助下,我逐步完成了自己的论文和程序,从导师身上也学习到很多知识,和经验,这些知识和经验令我受益匪浅。也从导师身上看到了自己的不足,不论是在即使层面上还是在对待工作的态度上,倒数如同明镜一般照出了我的缺点我的不足。此外,我还要感谢在我实习期间在论文和程序上帮助过我的同学和社会人士,此前我对于springboot开发方面的一些知识还不了解,是他们在我编写程序过程中给了我很多的启发和感想,也帮助了我对于程序的调试和检测。没有他们我是不能顺利完成本次毕业设计的。至此,我的毕业设计就花上了一个圆满的句号了。
[1]王晓彤.基于微信小程序构建心电诊断学线上教学平台的探索[J].牡丹江医学院学报,2023,44(01):170-172+175.DOI:10.13799/j.cnki.mdjyxyxb.2023.01.024.
[2]恒佳.钓鱼有益于心理健康[J].健与美,2023(02):22.
[3]谭明亮,代玲林.基于微信小程序的医院医疗设备管理系统设计与实现[J].价值工程,2023,42(03):137-140.
[4]Maruti Endang Sri,Yulianto Bambang,Suhartono Suhartono,Yohanes Budinuryanta,Cahyono Bambang Eko Hari. Scale development as a measuring tool of critical Javanese language’ awareness for pre-service Javanese teachers[J]. Cogent Arts & Humanities,2022,9(1).
[5]本刊编辑部.钓鱼人的年终总结[J].垂钓,2022,22(12):4-5.
[6]李乐.Java语言应用研究[J].智慧中国,2022(09):80-81.
[7]宋旸.使用Java语言开发Web应用软件的知识探讨[J].中国设备工程,2022(14):121-123.
[8]曹秀丽.智慧教学在“Java语言课程”中的应用探索[J].信息系统工程,2022(06):157-160.
[9]韩佳彤,杜芳,甄必鑫,张宏娜,乔鹏程,敖登巴拉,王春涛.基于SpringBoot的分布式市政运维分析平台[J].内蒙古大学学报(自然科学版),2022,53(03):309-316.DOI:10.13484/j.nmgdxxbzk.20220312.
[10]张宁.钓鱼(英文)[J].阅读,2022(36):49.
[11]朱言强. 钓鱼知识服务系统的构建[D].东北林业大学,2022.DOI:10.27009/d.cnki.gdblu.2022.001570.
[12]杨宇,徐万明.基于Springboot微信小程序用户管理系统设计[J].电脑与电信,2022(03):63-67.DOI:10.15966/j.cnki.dnydx.2022.03.023.
[13]曹嵩彭,王鹏宇.浅析Java语言在软件开发中的应用[J].信息记录材料,2022,23(03):114-116.DOI:10.16009/j.cnki.cn13-1295/tq.2022.03.009.
[14]田松涛,段元梅.基于SpringBoot的线上商城平台设计[J].无线互联科技,2022,19(01):56-57.
[15]Ma Jinfeng,Zhang Jing,Li Ruonan,Zheng Hua,Li Weifeng. Using Bayesian optimization to automate the calibration of complex hydrological models: Framework and application[J]. Environmental Modelling and Software,2022,147.
[16]Siyi Liu. Explore Java Language and Android Mobile Software Development[J]. International Journal of Frontiers in Engineering Technology,2021,3.0(2.0).
[17] Cao Tianze, Pan Jiazhi. Portal system design based on microservices and WeChat applet [J]. Science and Technology Innovation, 2020(18):89-90.
[18] Xiong Yu. Research and implementation of source code homology analysis technology for Java language [D]. Beijing University of Posts and Telecommunications, 2020.DOI:10.26969/d.cnki.gbydu.2020.000675.
[19] Zhou Feng. Research on Java language program security vulnerability detection technology [D]. Beijing University of Posts and Telecommunications, 2018.
[20] Yang Zhemin. Program vulnerability detection and diagnosis technology in Java language [D]. Fudan University, 2012.
The deceased is like a man who never gives up day and night. In the blink of an eye, college life is coming to an end. Facing parting and ending, people are always full of reluctance and confusion. I am also the same. I still remember that autumn, I couldn’t wait to arrive at the school a day early and faced the majestic campus. The door, my heart is full of expectations: Is this the starting point of my new life? That day, the sun was shining brightly, and the school's welcome ceremony was very warm. I faced my classmates who were smiling at me, as if rays of sunshine shone through my chest into my heart. At the same time, I met my lovely roommate that day, and we joined hands. We spent these two unforgettable two years together. Now, as I look at the acknowledgments of this paper, I can’t help but ask myself: Are we saying goodbye now?
I feel inexplicable and don't know what to say. I remember when I first came to school, I always thought that the engineering school would be too rigid and lack some tenderness. At that time, I was even a little bit repelled. But as I slowly got to know and understand the school, I realized that Her beauty, her tenderness, and I slowly fell in love with this campus, but time passed so quickly that I had to leave before I could fully appreciate her beauty, but the memories she brought to me will never be forgotten. If she leaves me, maybe my eyes will be filled with tears on the day she truly leaves. It’s not because I’m sad, I just want her image to be reflected in my tears and engraved in my heart. Finally, I would like to thank my teachers for teaching us knowledge and principles of life; thank you to my roommates for staying with me for so long; thank you to everyone who cares and supports me.
Young man, chase the wind and the moon without stopping. Wherever there is plain wasteland, there are spring mountains.
To receive the project source code for free, please follow and like + private message