PHP teahouse management system
With the development of society, all walks of life in society are taking advantage of the information age. The advantages and popularity of computers have necessitated the development of various information systems.
The main modules of the teahouse management system include viewing carousels, public message management, system user management (administrators, ordinary users), resource management (teahouse information, information classification), communication management (online communication, communication classification) mall Management (teahouse mall, category list, order list) module management (teahouse activities, logistics information, evaluation information) and other functions. Administrators in the system are mainly responsible for storing and managing various types of information safely and effectively. They can also manage, update and maintain the system, and have corresponding operating permissions for the backend.
In order to realize the various functions of the tea house management system, we need the strong support of the background database. A large amount of data such as the administrator's verification of registration information, the collected user information, and the associated information derived from the analysis are all managed by the database. In this article, the database server uses Mysql as the backend database, which closely connects the Web and the database. During the design process, the system code was fully guaranteed to have good readability, practicality, easy scalability, versatility, easy later maintenance, easy operation, and simple page.
The development of this system makes it more convenient and faster to obtain teahouse management system information, and also makes the teahouse management system management information more systematic and orderly. The system interface is friendly and easy to operate.
Keywords:Teahouse management system; PHP language; Mysql database
PHP tea house management system
Abstract
With the development of society, all walks of life in society are taking advantage of the advantages of the information age. The superiority and spread of computers necessitated the development of various information systems.
Tea house management system, the main modules include viewing carousel map, public message management, system user management (administrator, ordinary user), resource management (tea house information, information classification), communication management (online communication, exchange classification), mall management (tea house mall, classification list, order list) module management (tea house activities, logistics information, evaluation information) and other functions. The administrator in the system is mainly to safely and effectively store and manage all kinds of information, but also can manage the system and update maintenance and other operations, and has corresponding operation permissions for the background.
In order to realize the functions of the tea house management system, it needs the strong support of the background database. A large amount of data such as registration information, collected user information, and associated information obtained from this analysis is managed by the database. In this article, the database server side uses Mysql as the background database to closely link the web and the database. In the design process, the system code is fully guaranteed to have good readability, practicality, easy extensibility, versatility, easy maintenance, convenient operation and concise pages.
The development of this system makes it more convenient and fast to obtain tea house management system information, and also makes the tea house management system management information more systematic and orderly. The system interface is friendly and easy to operate.
Keywords: tea house management system; PHP language; MySQL database
Table of contents
2 System development environment
2.2 Implementation method of accessing database
2.3 PHP’s two-minute connection method to MySQL database
3.1 Technical feasibility: technical background
Table address (shipping address:)
Table article (article: article for content management system)
Table article_type (article classification)
Table auth (user rights management)
Table evaluation_information (evaluation information)
Table forum_type (forum classification)
Table goods (product information)
Table logistics_information (logistics information)
Table ordinary_users (ordinary users)
Table tea_house_activities (tea house activities)
Table tea_house_mall (Tea House Mall)
Table user (user account: used to save user login information)
Table user_group (user group: used for user front-end identity and authentication)
5.2 Administrator function module
5.3 User background function module
1 System Overview
1.1 Overview
With the rapid development of society, the impact of computers is comprehensive and profound. With the continuous improvement of people's living standards, people's requirements for teahouse management in daily life are also constantly increasing, and the number of people who need teahouse management is constantly increasing, making the development of teahouse management systems a necessary and urgent matter. The teahouse management system mainly uses computers to manage the information required by the teahouse management system to increase user choices. It also facilitates timely query and modification of user information and timely understanding of user information.
The tea house management system brings more convenience to users. The system cooperates with the database management system software to meet the needs of users.
1.2 Significance of the topic
Our country is the hometown of tea. China has a history of drinking tea for 4,000 years, and tea culture has a long history in China. The origin of tea in China can be traced back to Shennong, and the real rise of tea was in the Tang and Song Dynasties. When Chinese people drink tea, what they drink is not about the quality of the tea. The Chinese people focus on "taste" when drinking tea. What they appreciate in tea is not only the taste of tea, but also their understanding and taste of life and nature. As a medium for transmitting tea culture, teahouses are also essential in modern life. In modern society where material desires are rampant and the pace of life is accelerating. People urgently need a quiet, comfortable and clean place to relax their spirits and relieve themselves from the heavy work and life pressure. This is how the teahouse was born.
1.3 Main content
The teahouse management system conducts demand analysis from the aspects of functions, data processes, feasibility, and operating environment. The database and functions of the teahouse management system were designed in detail. The main interface design and related component design are analyzed, and the specific implementation of the teahouse management system is introduced.
Php technology is used to obtain data from the database and write data to the database, so that the system can directly perform various operations on the database and add dynamic content to the web page, thereby realizing various basic functions required by the teahouse management system.
2 System development environment
2.1 PHP technology
2.1.1 Introduction to PHP
PHP, or Hypertext Processor, is interpreted using a Web server-side scripting language. The Web server-side scripting language is relatively easy to use. HTML installs PHP syntax for Unix shells, C, C++, Php and Perl and PHP is incorporated into traditional CGI or Perl. PHP's simple syntax rules are more efficient than asset development. Additionally, PHP programs are encouraged to be more dynamic and new libraries can be expected to be added. PHP4.0 is completely open source code.
Currently, less than a dozen scripting languages can be used on the server side of the web, but the more commonly used ones are only compared to a limited number of other scripting languages such as PHP, ASP, Perl, JSP, and JSP. PHP has its own advantages:
(1) Cost;
(2) Based on the server;
(3) Strong support from database;
(4) The most powerful and significant feature of PHP is that it can support a large number of databases, which makes it easier to write a network-based database;
(5) Simple and effective. PHP, the basic programming language, adheres to rules that are simple and effective, yet its activities are powerful enough to help any type of website. This is different from Php's Perl, C++ and other programming languages.
(6) Network protocols and support for the following communication protocols are encouraged in this regard including:
①Email: IMAP, POP3,
②NMS，SNMP，
③Online News: NNTP
④Sharing account: NIS;
⑤International News Network: HTTP and Apache,
⑥ Protocol LDAP directory, as well as other functions related to the network.
Furthermore, it can be easily ported to other operating systems, bringing CGI PHP back to the program on the website.
2.1.2PHP development platform
PHP is supported as most programs in Linux operating system, Apache web server, MySQL database (light) operating system. Powerful free software or hardware required, Linux and Apache are perfect for small and medium-sized platforms. Required software:
(1) PHP language source code.
(2)MySQL source code
(3)Apache source code
This program is a free software, so after installing the software under the Linux operating system (you need to choose to install the corresponding package), it is particularly good for the environment as soon as you start installing this flexible service. Apache to start the service: start service httpd start the MySQL database: mysqld_safe - user = a good thing after all MySQL PHP programs can be used to treat Mozilla browser.
2.1.3PHP file composition
* PHP file The end of the Dreamweaver file processed by PHP is a text file that can be used.
In general, HTML tags and JQuery, PhpScript or PHP come together to reject standards brought in by law. Example shown below:
<？ PHP
"Hello world my first PHP program!" shows;
？>
2.2 Implementation method of accessing database
(1) First introduce the web database architecture:
As shown in Figure 2-1:
Figure 2-1 web database architecture
Basic steps for searching the web:
Step 1: Check the consumer’s data,
Step 2: You must establish a connection to the database;
Step 3: Search the database;
Step 4: Structure of data;
Step 5: The user's results are shown.
(2) The system until my MYSQL5.0 PHP integrated development environment, such as using WAMP server is turned on, and it is easier to access the database report development environment:
A connection to the MySQL database server Mysql_connect-;
Syntax: resource mysql_connect(host, username, password);
Please select the database: mysql_select_db (the name of the database link identifier);
Close the database: mysql_close();
2.3 PHP’s two-minute connection method to MySQL database
Active MySQL/MySQL library, or using the ODBC interface, the PHP MySQL database is a two-way link. Permanent and non-permanent connections.
(1) Permanent connection: The biggest advantage of a more permanent connection request is that it can be very effective for the client to stand in close contact, even better when connecting to the MySQL server. This process is done during the drafting of the page, not just at any time, but only during the lifetime of the connection request to the MySQL server, once connected. This sub-process is to establish a separate connection to the server which can be permanent.
(2) Non-permanent connection: it is a short circuit. The submission goes down to the web server, the server handles the request and sends the requested page to the browser you want to send to the client, and then the connection drops. For most websites, it is often related to the efficiency of the connection being used in most cases, but it is a full time to avoid any problems and to increase the server capacity.
2.4 MySql database
Mysql's language is unstructured and users can work on data. MySQL has attracted much attention because of its speed, reliability and adaptability. Most people agree that MySQL is the best choice for managing content without the need for transactional processing. And because Mysql's language and structure are relatively simple, but its functions and amount of stored information are very powerful, it has been widely used.
The role of Mysql database in the programming process is very extensive, bringing great convenience to users for data query. The application of Mysql database is highly flexible and powerful, so only a small piece of code is needed to implement a certain function, unlike other programs that require writing large pieces of code. Generally speaking, the language of Mysql database is relatively simpler.
Data process analysis is primarily a repository of data storage, which is performed on a computer rather than a real-life repository. Data is stored in a fixed format, not in an unordered manner. The definition is: it has a fixed format for a long time and can be stored in a shared computer memory. Database management mainly includes data storage, modification and addition, and the establishment of data tables. In order to ensure the normal operation of system data, some capable processors can manage it without requiring professional people to handle it. The establishment of the data table can adjust the data in the data table, recombine and reconstruct the data to ensure the security of the data. Due to the powerful functions of the database, the development of this system mainly uses Mysql for data management.
3 Demand analysis
3.1 Technical Feasibility: Technical Background
The teahouse management system is developed and used in the Windows operating system, and the current performance of PCs can already be used as web servers for ordinary websites. The technology used in system development is also owned by itself, and it is also one of the widely used technologies today.
The development environment and configuration of the system can be installed by yourself. The system uses Php development tools and the relatively mature Mysql database to interact with the system front-end and back-end data. The database is modified and maintained according to the technical language and combined with the needs, which can make the website The operation is more stable and secure, thereby completing the development of the website.
Hardware feasibility analysis: The design of the teahouse management system and information analysis does not have any rigid requirements for the computer used. As long as the computer can be used normally for code writing and page design, it is feasible. The main requirements are for the server and the platform. There are certain requirements after setting up the server to be uploaded. The server must be selected with relatively high security, and then opening the website must be smooth and cannot be paused for too long; it must be cost-effective and secure.
Therefore, we conducted a feasibility study and could see that there were no problems in developing the system.
3.2 Economic feasibility
The market research conducted before the development of the tea house management system and other related management systems are free of charge. All investigations and research are done by the developers themselves, and all work is done by themselves. When encountering problems that are difficult to solve by themselves, most of them solve related problems with the help of their instructors and classmates. Therefore, the development of a teahouse management system is completely economically feasible without any expense.
Using relatively mature technology, the system is developed based on PHP technology and uses Mysql database. Therefore, the system does not require high development manpower and financial resources and is economically feasible.
3.3 Operational feasibility:
Operability is mainly about the user experience after the design of the teahouse management system is completed, and the administrator can manage relevant data information at any time through the system, and both the administrator and user roles can be entered simply and clearly Go to your own system interface, and you can operate the functional modules simply and clearly through the interface navigation menu, which facilitates the user's information operation needs and the administrator's management of data information. For the operation of the system, no professional is required to directly operate and manage the functional modules, so the operability of the teahouse management system is completely acceptable. The operation of this system also uses the interface window to log in, so as long as the operator knows simple computer operations, it is completely fine.
3.4 System design rules
This tea house management system adopts PHP technology and Mysql database development, which fully ensures the stability and integrity of the system.
The design ideas for the design and implementation of the teahouse management system are as follows:
- The operation is simple and convenient, and the system interface is safe and good: the simple and clear page layout makes it easy to query relevant information managed by the teahouse management system.
2. Instant visibility: The information processed by the tea house management system will be immediately available for query at the corresponding location, thereby realizing the system function of "instant release and immediate results".
3. Complete functions: can manage the backend homepage, carousel pictures, public message management, system user management (administrators, ordinary users), resource management (teahouse information, information classification), communication management (online communication, communication classification) ) Mall management (teahouse mall, category list, order list) module management (teahouse activities, logistics information, evaluation information) and other management module modification and maintenance operations.
3.5 System process and logic
System business flow chart, as shown in the figure:
Figure 3-1 Login flow chart
Figure 3-2 Add information flow chart
Figure 3-3 Registration information flow chart
4 System outline design
4.1 Overview
Teahouse Management System is based on the Web service model and is a model structure suitable for the Internet environment. As long as members can connect to the Internet, they can use this system without being restricted by time or location. Tea House Management SystemWorking principle diagram, as shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure
The system architecture diagram belongs to the system design stage. The system architecture diagram is only a product of this stage. The overall architecture of the system determines the model of the entire system and is the foundation of the system. The overall structural design of the tea house management system is shown in Figure 4-2.
Figure 4-2 System structure diagram
4.3. Database design
4.3.1 Database entities
Administrator information structure diagram, as shown in Figure 4-3:
Figure 4-3 Administrator information entity structure diagram
UserInformation management entity attribute diagram, as shown in Figure 4-4:
Picture 4-4UseInformation managementProperty attribute picture
The entity attribute diagram of Tea House Mall is shown in Figure 4-5.
Figure 4-5 Teahouse Mall entity attribute diagram
4.3.2 Database design table
Convert the E-R diagram of the database conceptual design into a relational database. In a relational database, data relationships are composed of data tables, but the structure of the table is represented by the fields of the table.
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 (article: article for content management system)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
article_id |
mediumint |
8 |
0 |
N |
AND |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
AND |
Title: [0,125] is used in the title tag of articles and html |
|
| 3 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Article classification: [0,1000] is used to search for articles of the specified type |
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: [0,1000000000] Number of people who visited this article |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 6 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 8 |
source |
varchar |
255 |
0 |
AND |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
AND |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
AND |
N |
Tag: [0,255] is used to mark the relevant content of the article. Multiple tags are separated by spaces. |
|
| 11 |
content |
longtext |
2147483647 |
0 |
AND |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
AND |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
AND |
N |
Article description |
Table article_type (article classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
AND |
Category ID: [0,10000] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] determines the order in which categories are displayed. |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 4 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 5 |
description |
varchar |
255 |
0 |
AND |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
AND |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
AND |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 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 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 |
页面标题： |
|
| 6 |
path |
varchar |
255 |
0 |
Y |
N |
路由路径： |
|
| 7 |
position |
varchar |
32 |
0 |
Y |
N |
位置： |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
跳转方式： |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
是否可增加： |
| 10 |
del |
tinyint |
3 |
0 |
N |
N |
1 |
是否可删除： |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
是否可修改： |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
是否可查看： |
| 13 |
field_add |
text |
65535 |
0 |
Y |
N |
添加字段： |
|
| 14 |
field_set |
text |
65535 |
0 |
Y |
N |
修改字段： |
|
| 15 |
field_get |
text |
65535 |
0 |
Y |
N |
查询字段： |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
Y |
N |
跨表导航名称： |
|
| 17 |
table_nav |
varchar |
500 |
0 |
Y |
N |
跨表导航： |
|
| 18 |
option |
text |
65535 |
0 |
Y |
N |
配置： |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表cart (购物车)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
cart_id |
int |
10 |
0 |
N |
Y |
购物车ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
img |
varchar |
255 |
0 |
N |
N |
0 |
图片： |
| 4 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID： |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 7 |
state |
int |
10 |
0 |
N |
N |
0 |
状态：使用中，已失效 |
| 8 |
price |
double |
9 |
2 |
N |
N |
0.00 |
单价： |
| 9 |
price_ago |
double |
9 |
2 |
N |
N |
0.00 |
原价： |
| 10 |
price_count |
double |
11 |
2 |
N |
N |
0.00 |
总价： |
| 11 |
num |
int |
10 |
0 |
N |
N |
1 |
数量： |
| 12 |
goods_id |
mediumint |
8 |
0 |
N |
N |
商品id：[0,8388607] |
|
| 13 |
type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类： |
| 14 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]用于产品规格描述 |
表collect (收藏)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
collect_id |
int |
10 |
0 |
N |
Y |
收藏ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
收藏人ID： |
| 3 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 4 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 6 |
title |
varchar |
255 |
0 |
Y |
N |
标题： |
|
| 7 |
img |
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 |
更新时间： |
表comment (评论)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
comment_id |
int |
10 |
0 |
N |
Y |
评论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： |
表evaluation_information (评价信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
evaluation_information_id |
int |
10 |
0 |
N |
Y |
评价信息ID |
|
| 2 |
order_no |
varchar |
64 |
0 |
Y |
N |
订单编号 |
|
| 3 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 4 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 5 |
commodity_price |
varchar |
64 |
0 |
Y |
N |
商品价格 |
|
| 6 |
buying_users |
int |
10 |
0 |
Y |
N |
0 |
购买用户 |
| 7 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 8 |
evaluation_score |
varchar |
64 |
0 |
Y |
N |
评价分数 |
|
| 9 |
evaluation_content |
text |
65535 |
0 |
Y |
N |
评价内容 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表forum (论坛)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
forum_id |
mediumint |
8 |
0 |
N |
Y |
论坛id |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
排序 |
| 3 |
user_id |
mediumint |
8 |
0 |
N |
N |
0 |
用户ID |
| 4 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 5 |
praise_len |
int |
10 |
0 |
Y |
N |
0 |
点赞数 |
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
访问数 |
| 7 |
title |
varchar |
125 |
0 |
N |
N |
标题 |
|
| 8 |
keywords |
varchar |
125 |
0 |
Y |
N |
关键词 |
|
| 9 |
description |
varchar |
255 |
0 |
Y |
N |
描述 |
|
| 10 |
url |
varchar |
255 |
0 |
Y |
N |
来源地址 |
|
| 11 |
tag |
varchar |
255 |
0 |
Y |
N |
标签 |
|
| 12 |
img |
text |
65535 |
0 |
Y |
N |
封面图 |
|
| 13 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文 |
|
| 14 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 16 |
avatar |
varchar |
255 |
0 |
Y |
N |
发帖人头像： |
|
| 17 |
type |
varchar |
64 |
0 |
N |
N |
0 |
论坛分类：[0,1000]用来搜索指定类型的论坛帖 |
表forum_type (论坛分类)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
type_id |
smallint |
5 |
0 |
N |
Y |
分类ID：[0,10000] |
|
| 2 |
name |
varchar |
16 |
0 |
N |
N |
分类名称：[2,16] |
|
| 3 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该分类的作用 |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
外链地址：[0,255]如果该分类是跳转到其他网站的情况下，就在该URL上设置 |
|
| 5 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
上级分类ID：[0,32767] |
| 6 |
icon |
varchar |
255 |
0 |
Y |
N |
分类图标： |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
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： |
表logistics_information (物流信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
logistics_information_id |
int |
10 |
0 |
N |
Y |
物流信息ID |
|
| 2 |
order_no |
varchar |
64 |
0 |
Y |
N |
订单编号 |
|
| 3 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 4 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 5 |
commodity_price |
varchar |
64 |
0 |
Y |
N |
商品价格 |
|
| 6 |
buying_users |
int |
10 |
0 |
Y |
N |
0 |
购买用户 |
| 7 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 8 |
contact_number |
varchar |
64 |
0 |
Y |
N |
联系电话 |
|
| 9 |
ship_to_address |
varchar |
64 |
0 |
Y |
N |
收货地址 |
|
| 10 |
purchase_quantity |
varchar |
64 |
0 |
Y |
N |
购买数量 |
|
| 11 |
purchase_date |
date |
10 |
0 |
Y |
N |
购买日期 |
|
| 12 |
total_order_price |
varchar |
64 |
0 |
Y |
N |
订单总价 |
|
| 13 |
order_status |
varchar |
64 |
0 |
Y |
N |
订单状态 |
|
| 14 |
sign_in_status |
varchar |
64 |
0 |
Y |
N |
签收状态 |
|
| 15 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 17 |
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 |
待付款 |
订单状态：待付款，待发货，待签收，已签收，待退款，已退款，已拒绝，已完成 |
表ordinary_users (普通用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
ordinary_users_id |
int |
10 |
0 |
N |
Y |
普通用户ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 3 |
user_gender |
varchar |
64 |
0 |
Y |
N |
用户性别 |
|
| 4 |
user_age |
varchar |
64 |
0 |
Y |
N |
用户年龄 |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表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已取消 |
表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 |
更新时间： |
表tea_house_activities (茶舍活动)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
tea_house_activities_id |
int |
10 |
0 |
N |
Y |
茶舍活动ID |
|
| 2 |
activity_name |
varchar |
64 |
0 |
Y |
N |
活动名称 |
|
| 3 |
activity_type |
varchar |
64 |
0 |
Y |
N |
活动类型 |
|
| 4 |
activity_time |
varchar |
64 |
0 |
Y |
N |
活动时间 |
|
| 5 |
event_location |
varchar |
64 |
0 |
Y |
N |
活动地点 |
|
| 6 |
activity_description |
text |
65535 |
0 |
Y |
N |
活动描述 |
|
| 7 |
event_cover |
varchar |
255 |
0 |
Y |
N |
活动封面 |
|
| 8 |
event_details |
longtext |
2147483647 |
0 |
Y |
N |
活动详情 |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表tea_house_mall (茶舍商城)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
tea_house_mall_id |
int |
10 |
0 |
N |
Y |
茶舍商城ID |
|
| 2 |
notice |
varchar |
64 |
0 |
Y |
N |
须知 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
cart_title |
varchar |
125 |
0 |
Y |
N |
标题：[0,125]用于产品html的标签中 |
|
| 5 |
cart_img |
text |
65535 |
0 |
Y |
N |
封面图：用于显示于产品列表页 |
|
| 6 |
cart_description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]用于产品规格描述 |
|
| 7 |
cart_price_ago |
double |
8 |
2 |
N |
N |
0.00 |
原价：[1] |
| 8 |
cart_price |
double |
8 |
2 |
N |
N |
0.00 |
卖价：[1] |
| 9 |
cart_inventory |
int |
10 |
0 |
N |
N |
0 |
商品库存 |
| 10 |
cart_type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类： |
| 11 |
cart_content |
longtext |
2147483647 |
0 |
Y |
N |
正文：产品的主体内容 |
|
| 12 |
cart_img_1 |
text |
65535 |
0 |
Y |
N |
主图1： |
|
| 13 |
cart_img_2 |
text |
65535 |
0 |
Y |
N |
主图2： |
|
| 14 |
cart_img_3 |
text |
65535 |
0 |
Y |
N |
主图3： |
|
| 15 |
cart_img_4 |
text |
65535 |
0 |
Y |
N |
主图4： |
|
| 16 |
cart_img_5 |
text |
65535 |
0 |
Y |
N |
主图5： |
|
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 18 |
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 |
更新时间： |
5 系统详细设计
5.1系统功能模块
茶舍管理系统，在系统首页可以查看首页、公告消息、茶舍资讯、在线交流、茶舍商城、茶舍活动、我的等内容进行详细操作，如图5-1所示。
图5-1系统首页界面图
茶舍商城，在茶舍商城页面可通过筛选、或排序等搜索商品信息，如：商品名称、图片、须知、商品简介、原价、卖价等信息，对需要的商品可进行加入购物车或立即购买等操作，如图5-2所示。
图5-2茶舍商城界面图
茶舍活动，在茶舍活动列表可通过下拉或排序等搜索茶舍活动信息，如：活动名称、活动类型、时间、地点、描述、封面图、活动详情等信息，可进行收藏等操作，如图5-3所示。
图5-3茶舍活动界面图
用户注册，在用户注册页面通过填写账户、设置密码、确认密码、昵称、邮箱、手机号、身份、用户性别、用户姓名、身份等内容进行用户注册操作，如图5-4所示。
图5-4用户注册界面图
我的，用户点击右上角“我的”可看到我的账户、我的收藏、订单、购物车、收货地址等信息，用户可以根据需要进行相应操作；如图5-5所示。
图5-5我的界面图
5.2管理员功能模块
管理员登录，管理员通过输入账户，密码，滑动滑块进行验证登录系统，如图5-6所示。
图5-6管理员登录界面图
管理员登录进入茶舍管理系统可以查看后台首页、轮播图、公消息管理、系统用户管理（管理员、普通用户）、资源管理（茶舍资讯、资讯分类）、交流管理（在线交流、交流分类）商城管理（茶舍商城、分类列表、订单列表）模块管理（茶舍活动、物流信息、评价信息）等内容进行详细操作，如图5-7所示。
图5-7管理员功能界面图
系统用户管理，在人员管理页面可以查看索引、头像、昵称、用户性别、用户年龄、用户姓名等内容，并可根据需要进行详情，添加、查询、修改或删除等操作，如图5-8所示。
图5-8系统用户管理界面图
茶舍资讯管理，在茶舍资讯管理页面可以查看索引、标题、文章分类、标签等信息，并可根据进行详情、添加、查询或删除等操作，如图5-9所示。
图5-9茶舍资讯管理界面图
交流管理，在交流管理页面可以看到在线交流+交流分类两个子功能模块，管理中可根据需要进行详情、添加、修改或删除等操作，如图5-10所示。
图5-10交流管理界面图
茶舍商城管理，在茶舍商城管理页面可以查看索引、标题、封面图、卖价、原价、商品库存、产品分类、须知、描述等内容，并可根据进行详情、添加或删除等操作，如图5-11所示。
图5-11茶舍商城管理界面图
订单列表管理，在订单列表管理页面可以查看用户的订单信息并添加物流信息，如：索引、商品名称、订单号、商品图片、价格、原价、购买数量、总价、联系人名称、联系人地址、订单状态等内容，并可根据进行详情、查询或删除等操作，如图5-12所示。
图5-12订单列表管理界面图
模块管理，管理员在模块管理栏可看到茶舍活动、物流信息、评价信息这三个子功能模块，管理员可根据需要进行相应的操作，如图5-13所示。
图5-13模块管理界面图
5.3用户后台功能模块
用户登录进入茶舍管理系统可以查看后台首页、模块管理（物流信息、评价信息）、个人信息等内容进行详细操作，如图5-14所示。
图5-14用户功能界面图
物流信息，在物流信息页面可以查看订单状态、签收状态等内容，并可根据进行详情查询、评价等操作，如图5-15所示。
图5-15物流信息管理界面图
评价信息：用户可在签收订单后进行评价，如图5-16所示。
图5-16评价界面图
6 系统测试
6.1系统测试的目的
程序设计不能保证没有错误，这是一个开发过程，在错误或错误的过程中都是难以避免的。虽然这是不可避免的，但我们不能使这些错误始终存在于系统中，错误可能会造成无法估量的后果，如系统崩溃，安全信息泄露，系统无法正常启动等，为了避免这些问题我们需要测试程序，在测试过程中发现问题并纠正它们，从而使系统更长时间稳定成熟。
本章的作用是发现这些问题，并对其进行修改，虽然耗时费力，但对于长期使用而言是非常重要和必要系统的开发。
软件在设计后必须进行测试，调试过程中使用的方法是软件测试方法。在开发新软件时，系统测试是检查软件是否合格的关键步骤，以及是否符合设计目标的参考。测试主要是查看软件中数据的准确性，正确的操作与否，以及操作的结果，还有哪些方面需要改进。
茶舍管理系统的实现，对于系统中功能模块的实现及操作都必须通过测试进行来评判系统是否可以准确的实现。在茶舍管理系统正式上传使用之前必须做的一步就是系统测试，对于测试发现的错误及时修改处理，保证系统准确无误的供给会员使用。
6.2系统测试方法
在对茶舍管理系统进行测试的时候在找到问题的情况下必须在第一时间找到解决问题的办法，不要存在侥幸的心理，这样才能让茶舍管理系统的质量可以过关，并且开发的周期会大大缩短，还有就是在测试时，不要出现重复性的错误，遇到一个错误问题，要将整个茶舍管理系统开发所牵扯的该问题都必须一一解决，提高茶舍管理系统的安全性、稳定性。
白盒测试与黑盒测试是测试中比较常用的两种方法。
①结构测试俗称白盒测试：这种测试是在对程序的处理过程与结构都有详尽谅解的前提下，顺从程序内部的逻辑而完成的系统测试，以确定系统中所有的通路都能够遵照设计要求正常工作，不出现任何偏差。
②功能测试又成黑盒测试：主要是针对程序功能能够按照设计正常实现的一种检测，在程序接口处进行，检测程序手法数据是否正常，与外部信息的交换是否完整。
6.3 测试结果
经过对一系列测试结果的有效分析，本平台开发系统符合会员的要求和需求。所有的基本功能相对齐全，操作起来简单方便，测试系统性能良好，作为大众化系统使用是比较值得推广宣传的。
本系统通过对php和Mysql数据库的简介，从硬件和软件两反面说明了茶舍管理系统的可行性，本文结论及研究成果如下：实现了php与Mysql相结合构建的茶舍管理系统，网站可以响应式展示。通过本次茶舍管理系统的研究与实现，我感到学海无涯，学习是没有终点的，而且实践出真知，只有多动手才能尽快掌握它，经验对系统的开发非常重要，经验不足，就难免会有许多考虑不周之处。比如要有美观的界面，更完善的功能，才能吸引更多的会员。
由于在此之前对于php知识没有深入了解，所以从一开始就碰到许多困难，例如一开始的页面显示不规范、数据库连接有问题已经无法实现参数的传递等等，不过通过在网上寻找有关资料以及同学的帮助下最后都得到了解决，在此过程中，我不仅学到了很多知识，也提高了自己解决问题的能力，尤其是学会如何从大量的信息中筛选出所需有用的信息，同时我更加深刻的体会到了，虽然书本上的大部分知识都是有价值，正确的，但实际上每个人编程的思路和对数据处理的方法、思想都是不同的，这就要求我们一定要通过实践才能找到解决问题的方案。在此次毕业设计活动中，我不断的提高了自己，也得到了宝贵的经验，我相信这些对我以后的发展都会有很大帮助。
Through the development of the tea house management system, I referred to many examples of related systems, learned from each other's strengths, and gradually improved the system. However, the system still has many shortcomings, which need to be further improved in the future. study.
Practice has proved that the teahouse management system has very good development prospects. After testing and operation, the system's functions are perfect, the interface is beautiful, easy to use, easy to operate, and it is mature in technology and theory.
The end of graduation project also means that four years of college life are coming to an end. A lot of effort was put into the completion of the tea house management system and how to make it better during the operation of the system. This time will be unforgettable for a lifetime.
During the period of graduation project, it is inseparable from the careful guidance of the instructor and the enthusiastic help of the students. Sometimes several students discuss together how to implement a certain functional module in the system, how to implement it better, or If the problem is not effectively solved, we will have no intention to do other things, which makes us full of motivation for learning.
As the graduation project is coming to an end, I would like to first thank my instructor for your guidance in my graduation project and thesis. Under your careful guidance, I can quickly master the relevant functions of the system. With your strong help, I can combine the knowledge in the textbook with my own projects and truly apply what I have learned. Thank you for often sacrificing your own time to guide me with your rich teaching and project experience. In class, you taught us how to study and taught us new knowledge. After class, you were as kind as a friend. You taught me a lot of truths and made me realize that I should be a person first and do things later. I would like to thank all the teachers who have taught me and devoted a lot of effort to me. It is your sincere teaching and rigorous teaching that enabled me to successfully complete my studies. I would like to express my deep gratitude to you. Thank you to every teacher who taught me in college, and I sincerely wish you all the best.
I would also like to thank my comrades, that is, my classmates for their strong support and help. It is precisely because of your constant help and encouragement, staying up all night, constantly debugging and testing the program, that gave me great motivation to finally complete the operation of the website. The time we spend communicating and talking together will be our precious treasure on the road to the future. I want to thank you deeply!
Graduation is around the corner. In my future work and life, I will remember the teachings of my teachers and the help of my classmates, and continue to work tirelessly and pursue my goals to repay everyone who has supported and helped me!
Finally, I would like to express my deep gratitude to all the teachers who sacrificed their rest time to review, comment and participate in the thesis defense of this article. Here, thank you from the bottom of my heart!
[1] Zhang Liping. Research on PHP dynamic website development technology under the background of "Internet +" [J]. Wireless Internet Technology, 2022, 19(16): 154-156.
[2] Zhao Wantong. Dynamic website design and implementation based on PHP and MySQL [J]. Computer Programming Skills and Maintenance, 2022(08):103-105+109.DOI:10.16184/j.cnki.comprg.2022.08.022.
[3] Zheng Jiming, Dong Yunchao, Liu Qing. Discussion on the import and export methods of MySQL database data [J]. Computer Knowledge and Technology, 2022, 18(22): 24-25. DOI: 10.14004/j.cnki.ckt. 2022.1517.
[4] Yang Zhuofan. Research on data storage efficiency based on different storage engines of MySQL [J]. Computer Knowledge and Technology, 2022, 18(21): 18-20. DOI: 10.14004/j.cnki.ckt.2022.1232.
[5] Zhang Jun. Dynamic application of MySQL database in PHP web pages [J]. Integrated Circuit Applications, 2022, 39(06): 112-113.DOI: 10.19339/j.issn.1674-2583.2022.06.043.
[6] Mo Weiwei, Zhang Tao. Research on the application of PHP technology in enterprise website development [J]. Modern Industrial Economy and Informatization, 2022, 12(05): 158-159+234.DOI: 10.16525/j.cnki .14-1362/n.2022.05.065.
[7]Wu Daiwen. The Application and Management System of Scientific Research Projects Based on PHP and MySQL[J]. Journal of Interconnection Networks,2022,22(Supp02).
[8] Liu Jun. Dynamic web page design based on PHP technology [J]. Information Recording Materials, 2021, 22(10):142-143.DOI:10.16009/j.cnki.cn13-1295/tq.2021.10.068.
[9] Xiong Hui. Web dynamic web page design with PHP technology and MYSQL database technology [J]. Information Recording Materials, 2021, 22(01): 115-116. DOI: 10.16009/j.cnki.cn13-1295/tq. 2021.01.078.
[10] Liu Qianqian. Website design and implementation based on PHP and MySQL [J]. Small and medium-sized enterprise management and technology (late issue), 2020(10):162-163.
[11] Shi Ning. Research on the design of new business teahouse service system[D]. South China University of Technology, 2020.DOI:10.27151/d.cnki.ghnlu.2020.005320.
[12] Xu Sha. A brief discussion on teahouse space design from the ancient Chama Road [J]. Northern Literature, 2018(20):168.
[13]Li L.. Application of PHP technology in student PE score management system[J]. IPPTA: Quarterly Journal of Indian Pulp and Paper Technical Association,2018,30(8).
[14] Yilishati. Design of restaurant and teahouse management system based on .NET [J]. Information and Computers (Theoretical Edition), 2017(19):126-127.
[15]Krill, Paul. Zend paves new path to get PHP applications on the Web[J]. InfoWorld.com,2015.
[16]Shun Hui Wang,Jie Zou. Dynamic Interaction System Design of Urban Landscape Information Based on PHP Technology[J]. International Journal of Smart Home,2015,9(6).
[17] Liu Bin. Design and implementation of tea house management system based on Spring MVC framework [D]. Jilin University, 2015.
[18] Liu Yang. Development, design and implementation of teahouse management system based on MFC framework [D]. University of Electronic Science and Technology of China, 2012.
To receive the project source code for free, please follow and like + private message