Summary
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. Tourist attraction sharing website design, the main modules include viewing the backend homepage, carousel chart (carousel chart management), website announcement management (website announcement), resource management (travel information, information classification), mall management (commodity center, classification list) , order list), system users (administrators, registered users), module management (region management, attraction classification, room type management, attraction information, attraction ticket purchase, hotel information, hotel reservation, travel sharing) 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 tourist attraction sharing website, 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 management user consultation. The database used in this system is Mysql, which is built using the koa technology of node.js and realizes all the functions of this system. 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 the management information of tourist attractions sharing websites, and also makes the management information of tourist attractions sharing websites more systematic and orderly. The system interface is friendly and easy to operate.
Keywords: tourist attraction sharing website; koa technology; MySQL database
Node.js Tourist Attraction Sharing Website
Abstract
With the development of society, all walks of life in society are taking advantage of the advantages of the information age. The advantages and popularity of computers make the development of various information systems necessary. The main modules of the design of a tourist attraction sharing website include viewing the background homepage, rotating map (rotating map management), website announcement management (website announcement), resource management (travel information, information classification), mall management (commodity center, classification list, order list), system users (administrators, registered users) Module management (area management, scenic spot classification, room type management, scenic spot information, scenic spot ticket purchase, hotel information, hotel reservation, travel sharing) and other functions. The main purpose of administrators in the system is to store and manage various types of information safely and effectively. They can also manage, update, and maintain the system, and have corresponding operation permissions for the background.
To achieve the various functions of the tourist attraction sharing website, strong support from the background database is required. The administrator verifies the registration information, collects user information, and analyzes a large amount of data such as associated information, which are managed by the database management user consultation. The database used in this system is MySQL, and a management system is built using the koa technology of node.js, realizing all the functions of this system. During the design process, the system code has been fully guaranteed to have good readability, practicality, scalability, versatility, ease of later maintenance, easy operation, and concise pages.
The development of this system makes it easier and faster to obtain the management information of tourist attraction sharing websites, and also makes the management information of tourist attraction sharing websites more systematic and orderly. The system interface is friendly and easy to operate.
Key words: Tourist attraction sharing website; Koa technology; MySQL database
Table of contents
node.js tourist attraction sharing website
Node.js Tourist Attraction Sharing Website
1.1 Background and significance of topic selection
Chapter 2 Introduction to development tools and key technologies
2.3 Introduction to MVVM pattern:
2.4 Working principle of B/S system:
3.2.1 Technical feasibility: technical background
3.2.3 Operational feasibility:
3.4.2 Information addition process
3.4.3 Information deletion process
Chapter 4 System Design and Implementation
4.1 System architecture design
4.2 Development process design
Chapter 5 System Implementation
5.1 Front-end function module (front-end)
5.2 User function module (backend)
1.1 Background and significance of topic selection
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 the management of tourist attraction sharing websites in daily life are also constantly increasing, and the number of people who need to travel is constantly increasing, making the development of tourist attraction sharing website design a necessary and urgent matter. The design of tourist attraction sharing website mainly relies on computers to manage the information required for tourist attraction sharing website design to increase user choices. It also facilitates timely query and modification of user information and timely understanding of user reservation information. The design of the tourist attraction sharing website brings more convenience to users. The system cooperates with database software to meet the needs of users.
With the development of global informatization, people's life pace is getting faster and faster, and people pay more and more attention to the timeliness of information. Traditional tourist attraction sharing websites based on traditional publicity methods have long been unable to meet people's needs for information acquisition and convenience. Therefore, the design of tourist attraction sharing websites has gradually become the focus of people's attention. First of all, the design of tourist attraction sharing websites makes obtaining information online much more real-time and convenient than the traditional model. Once the system is online, no matter where in the world the user is, as long as they can connect to the Internet, they can get the information they want as soon as possible.
The application of computer technology in modern management has made computers an important tool for people to apply modern technology. It can effectively solve the problem of convenient and comprehensive acquisition of information and improve efficiency.
1.2 Research status
With the development of society and the advancement of science and technology, Internet technology is becoming more and more popular. The lifestyle spread through the Internet is gradually becoming more and more popular among the people. More and more Internet enthusiasts are beginning to meet their basic needs on the Internet, and at the same time, it is gradually entering the daily lives of various users. The Internet has many advantages such as convenience, speed, high efficiency and low cost. Therefore, similar to tourist attraction sharing websites, meeting the busy needs of users is not only a convenient way for users to view information at any time, but also improves management efficiency.
This article first takes the basic issues of the tourist attraction sharing website process as the research object. Before developing the system, we conducted a detailed survey and analysis of the existing situation. Finally, we used computer technology to develop a complete and suitable tourist attraction sharing website. The main advantages of the implementation of this system are: the system is mainly developed using computer technology, which is convenient and fast; the system can view all the user's information management through the administrator interface.
The tourist attraction sharing website software is a convenient, fast and practical information service query software. With the continuous popularization of intelligent networks in the global market and the use of various intelligent platforms, system development is related to people's daily needs. As China's mainstream intelligent technology development system, such software is naturally needed to meet the needs of more users and experience.
1.3 Research content
The development and implementation of a tourist attraction sharing website requires the following work:
(1) First, determine the topic, determine the system to be built, and conduct a preliminary systematic confirmation of the background of the system and some of the problems currently faced.
(2) After the system is confirmed, the technology used in system development is confirmed based on the system development needs. The development of this tourist attraction sharing website uses koa technology, the database is built and developed for the platform, and the technology used is confirmed for technical analysis. Whether the technology used can complete the implementation of the tourist attraction sharing website.
(3) Determine the technology used in the system, confirm online the user roles divided by the system, and determine the functional modules to be designed based on the user role division. The design of the tourist attraction sharing website system is mainly divided into administrator and user roles. The functional modules used are also different, but the content implemented by the system's database is interactive. Users can process course information according to their own needs at any time. System staff can process and operate online information according to their own assigned content. The administrator obtains detailed data information of all users and handles it as soon as possible according to needs.
(4) After the functional modules of the system are confirmed, the program and interface are designed. After the design is completed, tests are conducted to determine whether the program is perfect. For system testing, different users are required to edit and submit different content, and use different The testing method finds out the loopholes in the program and solves the loopholes in the program online. If there are no problems with the test system, the system can be uploaded for formal operation.
2.1 koa framework
Node.js is an asynchronous world. The official API supports asynchronous programming models in the form of callbacks, which will bring many problems, such as: 1. Callback nesting problems; 2. Callbacks may be called synchronously in asynchronous functions to return data. Brings inconsistency. In order to solve the above problems, Koa appeared.
Koa is built by the original team of Express and is committed to becoming a smaller, more expressive, and more robust web framework. Using koa to write web applications can avoid repeated and cumbersome nesting of callback functions and greatly improve the efficiency of error handling. Koa does not bind any middleware in the kernel method. It only provides a lightweight and elegant function library, making writing web applications easy. The development idea is similar to express. The biggest feature is that it can avoid asynchronous nesting.
Alibaba is using the Koa framework internally and has made some extensions and encapsulations based on Koa. And developed an open source framework egg based on koa.
2.2 Vue.js main functions:
Vue.js is a progressive framework for building user interfaces. Unlike other heavyweight frameworks, Vue adopts a bottom-up incremental development design. Vue's core library only focuses on the view layer, and is very easy to learn and integrate with other libraries or existing projects. Vue, on the other hand, is fully capable of driving complex single-page applications developed using single-file components and libraries supported by the Vue ecosystem.
The goal of Vue.js is to implement responsive data binding and composed view components through the simplest possible API.
Vue.js itself is not a full-featured framework - it only focuses on the view layer. Therefore it is very easy to learn and very easy to integrate with other libraries or existing projects. On the other hand, Vue.js can also power complex single-page applications when used with related tools and supporting libraries.
2.3 Introduction to MVVM pattern:
MVVM is the abbreviation of Model-View-ViewModel. It is essentially an improved version of MVC. MVVM abstracts the state and behavior of the View, allowing us to separate the view UI and business logic. Of course, ViewModel has already done these things for us. It can take out the data of the Model and help handle the business logic involved in the View due to the need to display content. Microsoft's WPF brings new technical experiences, such as Silverlight, audio , video , 3D , animation ..., which results in the software UI layer being more detailed and customizable. At the same time, at the technical level, WPF also brings new features such as Binding, Dependency Property, Routed Events, Command, DataTemplate, ControlTemplate and so on. The origin of the MVVM (Model-View-ViewModel) framework is a new architectural framework that evolved from the application method of combining the MVP (Model-View-Presenter) pattern with WPF . It is based on the original MVP framework and incorporates the new features of WPF to cope with increasingly complex changes in customer needs.
2.4 Working principle of B/S system:
The B/S architecture adopts the working mode of browser request and server response.
Users can access text, data, pictures, animations, video on demand, sounds and other information generated by Web servers on the Internet through a browser;
Each Web server can be connected to the database server in various ways, and a large amount of data is actually stored in the database server;
Download the program from the Web server to the local for execution. If you encounter instructions related to the database during the download process, the Web server will hand it over to the database server for interpretation and execution, and return it to the Web server, and the Web server will return it to the user. In this structure, many networks are connected together to form a huge network, that is, the global network. Each enterprise can build its own Internet based on this structure.
In the B/S mode, the user requests access through the browser to many servers distributed on the network. The browser's request is processed by the server, and the processing results and corresponding information are returned to the browser. Other data All processing and requests are completed by the Web Server. Through this framework structure and the browser embedded inside the operating system, this structure has become the mainstream structure pattern of today's software applications.
2.5 MySQL database
The language of Mysql is unstructured and users can work on the 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 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 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.
Chapter 3 System Analysis
3.1 Requirements analysis
Before any project is developed and researched, it is necessary to conduct a careful analysis of the needs of the R&D system itself. Market research cannot be ignored. The functional needs of users are determined from actual scenarios to clarify goals and develop the entire system. There is a more accurate positioning. In this chapter, it is necessary to analyze the system performance analysis, business process analysis, and data. The overall interface of the tourist attraction sharing website is simple and the functions are complete.
The feasibility of requirements is the analysis and discussion of what requirements a developed system can achieve. Whether the developed system platform meets the previous requirements. Only in pre-assessment of system development can requirements be completed before system development and implementation. If you don't have the feasibility of developing a system with substandard functionality, that's development failure. Whether the development system is useful and can complete the requirements discussed before, the actual requirements of the tourist attraction sharing website are analyzed below.
System design needs to start with the actual needs of users and administrators to understand what functions they need to implement and what administrative tasks they can include.
Taking into account the characteristics of the system design of tourist attraction sharing websites, several requirements should be met:
(1) It can carry out information management of tourist attractions sharing websites through the Internet and promote information management of tourist attractions sharing websites.
(2) Learning methods become more diverse and management becomes more standardized;
(3) It provides a free channel to ensure real-time and effective communication of data.
3.2 Feasibility analysis
3.2.1 Technical feasibility: technical background
The tourist attraction sharing website uses koa technology to develop a front-end application with complete functions and simple use, and establishes and maintains a back-end database system with complete data, security and strong stability.
The system uses koa technology and Mysql database as design tools, making it simple and easy to learn and operate. It is worth trying to develop a set of tourist attraction sharing websites by combining user roles. Data integrity and many qualities provide a basis for the function allocation and management of data. It is also an important part of the database security platform and an important means to improve and enhance data security. Additionally, to provide a smoother, smarter, and more efficient approach to basic control, the steps required to simultaneously build support for secure computing environments and help maintain security are defined. Because among these two development tools, the functions are powerful and free and the interface is good, so the tourist attraction sharing website is technically feasible.
3.2.2 Economic feasibility
The development of the tourist attraction sharing website management is developed by the developers themselves, and there is no need to purchase other software or ports. Moreover, the market research and other tourist attraction sharing websites done before the development of the tourist attraction sharing website management are all There is no cost. Through the developers' own efforts, all the work is done by themselves. When encountering problems that are difficult to solve by themselves, most of them use the help of classmates and instructors to solve relevant information, so for tourist attractions The development of sharing websites is completely economically feasible without any expenses.
Using koa technology is a relatively mature technology, so there is no economic problem in the development of tourist attraction sharing websites.
3.2.3 Operational feasibility:
Operability is mainly about the user experience after the tourist attraction sharing website system is designed. Administrators can manage relevant data information at any time through the system, and it can be simple and clear for the two user roles of administrators and users. Entering your own system interface, you can operate the functional modules simply and clearly through the interface navigation menu, which facilitates user information needs and course information management data information. For system operation, no professional is required to directly operate and manage the functional modules, so The operability of the system is completely fine. 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.3 Performance analysis
For performance analysis, compared with the traditional management method, which uses manual statistics and management of data information using paper and pen, and this method is more troublesome to store and search certain data information, as With the advent of computer networks, this traditional method is difficult to adapt to the development of current society. It not only reduces people's work efficiency, but also requires a lot of manpower and material resources. The time and cost of use are relatively high. In order to To reduce costs, improve user efficiency, and develop a set of tourist attraction sharing websites based on computer and network technology.
The development and design of the tourist attractions sharing website is an independent system, using popular databases for data storage and development. It is mainly to realize the user roles and corresponding functional modules of the tourist attractions sharing website, so that the management of the tourist attractions sharing website will not exist. Management differences and low efficiency are exactly the opposite of traditional management information. The implementation of tourist attraction sharing websites can save resources and improve business processing speed. It is fast, efficient and powerful.
3.4 System operation process
3.4.1 User login process
The first level of system security is that if users want to enter the system, they must enter their login information through the login window. Only after the information entered by the user is accurate can they enter the operating system interface and perform function modules. Corresponding operation, if the information entered by the user is incorrect, a prompt box will appear in the window, the user fails to log in, and returns to the first step to re-enter, as shown in Figure 3-1.
Figure 3-1 Login operation flow chart
3.4.2 Information addition process
For tourist attraction sharing websites, the required data information needs to be added at any time. For users to add information, they need to fill in the data information to be added according to the adding interface and the content of the selection box. After the information input is completed, it is judged whether the data information meets the requirements. If the requirements are added, if the information added by the user does not meet the requirements, you need to return to the first step, re-enter the data information, and then perform the judgment operation, as shown in Figure 3-2.
Figure 3-2 Information adding flow chart
3.4.3 Information deletion process
No matter which user role enters the different system operation interfaces, they can perform different information operation functions. For deletion of system data, once the user deletes the information, the deleted data will not be restored, so the user When deleting data, you must determine whether the deleted content is definitely to be deleted. After confirming that it is correct, select Confirm the deletion operation, as shown in Figure 3-3.
Figure 3-3 Information deletion flow chart
Chapter 4 System Design and Implementation
4.1 System architecture design
An overview and design analysis of the system project of the tourist attraction sharing website. The main content includes a specific analysis of the learning platform. The database is designed. The data uses a mysql database. The system design adopts a more humane operation design and the errors that occur in the system are avoided. Information can be processed and fed back in a timely manner.
The tourist attraction sharing website is based on existing mobile phones and can realize administrators: home page, carousel map (carousel map management), website announcement management (website announcement), resource management (travel information, information classification), mall management (commodity center) , classification list, order list), system users (administrators, registered users), module management (region management, attraction classification, room type management, attraction information, attraction ticket purchase, hotel information, hotel reservation, travel sharing), etc. and statistical analysis. The module relationship diagram established according to the system functional requirements is as follows:
Figure 4-1 Administrator function module diagram
4.2 Development process design
The development of tourist attraction sharing website. Analysis, writing, development, planning and operation of the management module and the database used by the system are the necessary three steps to build an information management application. It determines whether the system can truly realize the preset functions and whether it can Implement after successful design. During the development process, each stage must be developed strictly in a linear sequence, and each work generated at the corresponding stage can be verified and checked through technology. Ensure that the completion of one stage is correct and will not cause dragging in the next stage, ensuring that the system completes the design function.
Judging from the successful development experience of tourist attraction sharing websites, the above method has the most obvious effect and reduces the complexity of system development to the greatest extent. As shown in Figure 4-2.
Figure 4-2 Development system flow chart
4.3 Database design
Database is the foundation and core of information system. The quality of database design directly affects the success or failure of information system development. To create a database table, first determine the attributes of the entities and the relationships between them. Create a data table based on relationships.
4.3.1 Entity ER diagram
Database is the most important step in the entire software programming. For database problems, it is mainly to determine the number of databases and the creation of structural formulas. The display system uses Mysql to manage the database and ensure data security and stability.
Conceptual models are designed to abstract real-world information and model the information world. It is a powerful tool for database design. Database conceptual model design can describe the conceptual model of the real world through ER diagrams. An ER diagram of a system shows the links between entities in the system. Moreover, the Mysql database is a database with relatively strong self-protection capabilities. The following figure is mainly an ER diagram of database entities:
Figure 4-3 System ER diagram
These functions can fully meet the needs of tourist attraction sharing websites. This system has relatively comprehensive functions. The system function structure is shown in Figure 4-5.
Figure 4-4 System functional structure diagram
4.3.2 Data sheet
We can analyze according to the detailed analysis requirements of the data structure, we can analyze according to the requirements of the input and output data volume, determine what tables, the relationship between the structures, we can verify, adjust and improve, the query and browsing process can realize the database, In order to make users have more requirements for data and functions.
Based on the characteristics of the database used by the system, the conceptual model of the database was converted and constructed. However, this system only needs to fully consider the functions of the tourist attraction sharing website, and the organization is relatively clear.
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 |
Y |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
Y |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
Y |
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 |
Y |
Shipping address: |
|
| 2 |
name |
varchar |
32 |
0 |
Y |
N |
Name: |
|
| 3 |
phone |
varchar |
13 |
0 |
Y |
N |
cell phone: |
|
| 4 |
postcode |
varchar |
8 |
0 |
Y |
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 |
Y |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
Y |
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 |
Y |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
Y |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
Y |
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 |
Y |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
Y |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
Y |
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 |
Y |
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 |
Y |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
Y |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
Y |
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 attraction_information (attraction information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
attraction_information_id |
int |
10 |
0 |
N |
Y |
Attraction information ID |
|
| 2 |
attraction_name |
varchar |
64 |
0 |
Y |
N |
Attraction name |
|
| 3 |
attraction_type |
varchar |
64 |
0 |
Y |
N |
Attraction type |
|
| 4 |
region |
varchar |
64 |
0 |
Y |
N |
area |
|
| 5 |
photo |
varchar |
255 |
0 |
Y |
N |
photo |
|
| 6 |
ticket_price |
int |
10 |
0 |
Y |
N |
0 |
fare |
| 7 |
address |
varchar |
64 |
0 |
Y |
N |
address |
|
| 8 |
opening_hours |
varchar |
64 |
0 |
Y |
N |
开放时间 |
|
| 9 |
scenic_spot_hotline |
varchar |
64 |
0 |
Y |
N |
景区热线 |
|
| 10 |
surrounding_hotels |
text |
65535 |
0 |
Y |
N |
周边酒店 |
|
| 11 |
transportation_guide |
text |
65535 |
0 |
Y |
N |
交通指南 |
|
| 12 |
details |
longtext |
2147483647 |
0 |
Y |
N |
详情 |
|
| 13 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 14 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 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 |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
auth_id |
int |
10 |
0 |
N |
Y |
授权ID： |
|
| 2 |
user_group |
varchar |
64 |
0 |
Y |
N |
用户组： |
|
| 3 |
mod_name |
varchar |
64 |
0 |
Y |
N |
模块名： |
|
| 4 |
table_name |
varchar |
64 |
0 |
Y |
N |
表名： |
|
| 5 |
page_title |
varchar |
255 |
0 |
Y |
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 |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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]用于产品规格描述 |
表category_of_attractions (景点分类)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
category_of_attractions_id |
int |
10 |
0 |
N |
Y |
景点分类ID |
|
| 2 |
types_of_attractions |
varchar |
64 |
0 |
Y |
N |
景点类型 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
commodity_center_id |
int |
10 |
0 |
N |
Y |
商品中心ID |
|
| 2 |
model |
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 |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
添加人 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hotel_information_id |
int |
10 |
0 |
N |
Y |
酒店信息ID |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题 |
|
| 3 |
layout_of_a_house_or_an_apartment |
varchar |
64 |
0 |
Y |
N |
房型 |
|
| 4 |
region |
varchar |
64 |
0 |
Y |
N |
地区 |
|
| 5 |
photo |
varchar |
255 |
0 |
Y |
N |
照片 |
|
| 6 |
price |
int |
10 |
0 |
Y |
N |
0 |
价格 |
| 7 |
address |
varchar |
64 |
0 |
Y |
N |
地址 |
|
| 8 |
number_of_rooms |
int |
10 |
0 |
Y |
N |
0 |
客房数量 |
| 9 |
number_of_people_available_for_check_in |
varchar |
64 |
0 |
Y |
N |
可入住人数 |
|
| 10 |
room_facilities |
text |
65535 |
0 |
Y |
N |
房间设施 |
|
| 11 |
details |
longtext |
2147483647 |
0 |
Y |
N |
详情 |
|
| 12 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 13 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 14 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 15 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 16 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hotel_reservation_id |
int |
10 |
0 |
N |
Y |
酒店预订ID |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
订单号 |
|
| 3 |
title |
varchar |
64 |
0 |
Y |
N |
标题 |
|
| 4 |
layout_of_a_house_or_an_apartment |
varchar |
64 |
0 |
Y |
N |
房型 |
|
| 5 |
price |
varchar |
64 |
0 |
Y |
N |
价格 |
|
| 6 |
booking_quantity |
int |
10 |
0 |
Y |
N |
0 |
预订数量 |
| 7 |
booking_days |
int |
10 |
0 |
Y |
N |
0 |
预订天数 |
| 8 |
total_price |
varchar |
64 |
0 |
Y |
N |
总价格 |
|
| 9 |
user |
int |
10 |
0 |
Y |
N |
0 |
用户 |
| 10 |
check_in_date |
date |
10 |
0 |
Y |
N |
入住日期 |
|
| 11 |
contact_number |
varchar |
64 |
0 |
Y |
N |
联系电话 |
|
| 12 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 13 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 14 |
pay_state |
varchar |
16 |
0 |
N |
N |
未支付 |
支付状态 |
| 15 |
pay_type |
varchar |
16 |
0 |
Y |
N |
支付类型: 微信、支付宝、网银 |
|
| 16 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
待付款 |
订单状态：待付款，待发货，待签收，已签收，待退款，已退款，已拒绝，已完成 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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已取消 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
regional_management_id |
int |
10 |
0 |
N |
Y |
地区管理ID |
|
| 2 |
region |
varchar |
64 |
0 |
Y |
N |
地区 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
registered_users_id |
int |
10 |
0 |
N |
Y |
注册用户ID |
|
| 2 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 3 |
age |
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 |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
room_type_management_id |
int |
10 |
0 |
N |
Y |
房型管理ID |
|
| 2 |
layout_of_a_house_or_an_apartment |
varchar |
64 |
0 |
Y |
N |
房型 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间： |
表tickets_for_tourist_attractions (景点购票)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
tickets_for_tourist_attractions_id |
int |
10 |
0 |
N |
Y |
景点购票ID |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
订单号 |
|
| 3 |
attraction_name |
varchar |
64 |
0 |
Y |
N |
景点名称 |
|
| 4 |
ticket_price |
varchar |
64 |
0 |
Y |
N |
票价 |
|
| 5 |
attraction_type |
varchar |
64 |
0 |
Y |
N |
景点类型 |
|
| 6 |
purchase_quantity |
int |
10 |
0 |
Y |
N |
0 |
购买数量 |
| 7 |
total_price |
varchar |
64 |
0 |
Y |
N |
总价格 |
|
| 8 |
user |
int |
10 |
0 |
Y |
N |
0 |
用户 |
| 9 |
contact_number |
varchar |
64 |
0 |
Y |
N |
联系电话 |
|
| 10 |
pay_state |
varchar |
16 |
0 |
N |
N |
未支付 |
支付状态 |
| 11 |
pay_type |
varchar |
16 |
0 |
Y |
N |
支付类型: 微信、支付宝、网银 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
travel_sharing_id |
int |
10 |
0 |
N |
Y |
旅行分享ID |
|
| 2 |
line_name |
varchar |
64 |
0 |
Y |
N |
线路名称 |
|
| 3 |
route_theme |
varchar |
64 |
0 |
Y |
N |
线路主题 |
|
| 4 |
publicity_picture |
varchar |
255 |
0 |
Y |
N |
宣传图片 |
|
| 5 |
travel_video |
varchar |
255 |
0 |
Y |
N |
旅行视频 |
|
| 6 |
region |
varchar |
64 |
0 |
Y |
N |
地区 |
|
| 7 |
scenic_spots |
varchar |
64 |
0 |
Y |
N |
途径景点 |
|
| 8 |
per_capita_expenditure |
int |
10 |
0 |
Y |
N |
0 |
人均花销 |
| 9 |
share_users |
int |
10 |
0 |
Y |
N |
0 |
分享用户 |
| 10 |
traffic_arrangement |
text |
65535 |
0 |
Y |
N |
交通安排 |
|
| 11 |
schedule |
text |
65535 |
0 |
Y |
N |
时间安排 |
|
| 12 |
line_introduction |
longtext |
2147483647 |
0 |
Y |
N |
线路介绍 |
|
| 13 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 14 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 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 |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
文件类型 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
创建时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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.1前台功能模块（前端）
旅游景点分享网站登录界面，通过填写账号、密码、滑动滑块进程验证进行登录，如图5-1所示。
图5-1登录界面图
注册，通过填写账号、密码、确认密码、昵称、手机、身份、邮箱、用户姓名、用户性别、用户年龄等信息，输入完成后选择提交即可注册成功，如图5-2所示。
图5-2注册界面图
首页，可以进行首页、网站公告、旅游资讯、商品中心、景点信息、酒店信息、旅行分享等功能模块的查看与操作，如图5-3所示。
图5-3系统首页界面图
景点信息列表页面可以查看展示的景点名称、票价、景点类型、地址、景区热线、地区、开放时间、图片等信息，并可以进行购票、点赞、收藏、发表评论等操作，如图5-4所示。
图5-4景点信息列表界面图
5.2用户功能模块（后端）
在用户功能页面可以首页、商城管理（订单列表）、模块管理（景点购票、酒店预订、旅行分享）、个人中心等内容进行相对应操作，如图5-5所示。
图5-5用户功能界面图
景点购票管理，在景点购票页面可以编辑订单号、景点名称、票价、景点类型、购买数量、总价格、用户、联系电话等内容，并可根据需要进行支付、修改或删除操作，如图5-6所示。
图5-6景点购票界面图
酒店预订管理，在酒店预订页面可以查看订单号、标题、房型、价格、预订数量、预订天数、总价格、用户等内容，并可根据需要进行支付、修改或删除操作，如图5-7所示。
图5-7酒店预订界面图
旅行分享管理，在旅行分享页面可以查看线路名称、线路主题、宣传图片、旅行视频、地区、人均花销、途径景点、分享用户、交通安排、时间安排线路介绍等内容，并可根据需要进行查看评论、添加或删除操作，如图5-8所示。
图5-8旅行分享界面图
5.3管理员功能模块（后端）
旅游景点分享网站登录界面，通过填写账号、密码、验证等信息进行登录，如图5-9所示。
图5-9登录界面图
轮播图管理，管理员通过输入标题、轮播图等内容，根据详情进行添加、查询、删除等操作提交，如图5-10所示。
图5-10轮播图管理界图面
在管理员功能页面可以后台首页、轮播图（轮播图管理）、网站公告管理（网站公告）、资源管理（旅行资讯、资讯分类）、商城管理（商品中心、分类列表、订单列表）、系统用户（管理员、注册用户）、模块管理（地区管理、景点分类、房型管理、景点信息、景点购票、酒店信息、酒店预订、旅行分享）等内容进行相对应操作，如图5-11所示。
图5-11管理员功能界面图
用户管理，在用户管理页面可以编辑用户昵称、用户名、姓名、性别、年龄等内容，并可根据需要进行修改或删除操作，如图5-12所示。
图5-12用户管理界面图
旅行资讯管理，在旅行资讯页面可以查看标题、封面图、文章分类、标签等内容，并可根据需要进行查看评论、添加、修改或删除操作，如图5-13所示。
图5-13旅行资讯管理界面图
房型管理，在房型管理页面可以查看房型等内容，并可根据需要进行评论、添加、修改或删除操作，如图5-14所示。
图5-14房型管理界面图
酒店信息管理，在酒店信息管理页面可以查看标题、房型、地区、照片、价格、地址、客房数量、可入住人数、房间设施等内容，并可根据需要进行查看评论、添加、修改或删除操作，如图5-15所示。
图5-15酒店信息管理界面图
第六章 系统的测试
6.1 测试目的
程序设计不能保证没有错误，这是一个开发过程，在错误或错误的过程中难以避免，这是不可避免的，但我们不能使这些错误始终存在于系统中，错误可能会造成无法估量的后果 如系统崩溃，安全信息，系统无法正常启动，导致安装用户手机屏幕等，为了避免这些问题，我们需要测试程序，并发现这些问题，并纠正它们 ，并使系统更长时间稳定成熟，本章的作用是发现这些问题，并对其进行修改，虽然耗时费力，但长期非常重要和必要 系统的开发。
软件测试与开发过程是一样的，都必须按照软件工程的正规原理进行，遵守管理学理论。不过，目前国内的软件测试已经积累了大量经验和方法，步骤相对成熟，软件测试的效率也越来越高。
旅游景点分享网站的实现，对于系统中功能模块的实现及操作都必须通过测试进行来评判系统是否可以准确的实现。在旅游景点分享网站正式上传使用之前必须做的一步就是系统测试，对于测试发现的错误及时修改处理，保证系统准确无误的供给用户使用。
6.2 测试方案设计
6.2.1 测试策略
1、功能测试
从用户的角度来看，测试时不了解新开发软件的内部结构，因此可以将系统与黑匣子进行比较，盲目输入后可以查看系统给出的反馈。这种测试属于黑盒测试，在测试中如果输入错误信息系统会报错。
2、性能测试
测试软件程序的整体状况（称为性能测试）通常使用自动化测试工具来检测系统的整体功能，在负载测试和压力测试之间进行分配，在某些情况下，将这两种情况结合起来。虽然压力测试可以检测到系统可以提供的最高级别的服务，但负载测试可以测试系统如何响应增加的负载。
6.2.2 测试分析
测试评估系统质量的方法不局限于系统编码和过程，应该与软件设计工作和历史需求分析密切相关。
软件测试应遵循以下原则：
(1)软件测试应尽快进行，整个测试部分应在软件开发和设计的整个过程中进行。如发现错误，立即处理，将大大减少软件开发的时间，并提高软件的质量。
(2)在软件的各种测试中，测试过程中使用的计划、报告等应妥善处理和存储。其主要目的是为了便于以后系统的维护。
(3)软件测试整个过程中的聚类现象应优先考虑。
(4)对于软件测试，我们应该尽量不去和自己设计的系统进行参考，而是要测试对方的程序，以确保软件测试结果的客观性和公平性。
(5)整个测试计划严格按照软件测试的具体实施细则进行。
(6)对整个测试结果进行综合检查，尽量避免重复错误。
本旅游景点分享网站满足用户的要求和需求，本旅游景点分享网站的使用能够有效的提高用户的使用率。
6.3 测试结果
测试后得到的性能和用例，系统具有足够的正确性、可靠性、稳定性，并且可以对输入数据进行准确的点击操作处理和响应测试用户的体验也得到了很好的反馈和响应时间。合理的范围，可以兼容所有主流浏览器，设计所需的效果。
结 论
在这个设计中，我花了大量的时间去理解系统开发中使用的知识，经过这段时间的努力工作最终完成了系统设计。通过这一阶段的学习，我发现了自己的不足，充分掌握了必要的应用技能，进一步的学习使我充实了自己的知识基础，完成了这个艰巨的任务。当遇到问题时，我很及时的寻求老师的帮助，通过专业的网站和论坛来解决，他们的帮助让我一步一步的成功克服了困难的问题。系统设计过程不容易，你需要不断充实自己，有勇气克服困难。系统开发的一些功能还不完善，需要继续改善后，通过用户体验来修改设计完美的系统，让用户得到更好的体验，我觉得很高兴，因为这是我第一次通过自己的努力实现这个系统，但绝不是我的最后一个，在未来我将努力实现更多的优秀的系统。
在一些编程语言的系统实现中，对词汇表不太熟悉，导致了开发的困难，但是我通过了合适的字典软件来解决这个大问题。由此，我学会了自己的英语缺陷。在那之后，我不断地提高自己的英语知识，这样我就不会有任何未来的工作和生活。毕业设计过程我感觉很深刻，从一开始就不熟悉开发技术，一步一步的使用，接触到文献和信息，不难理解，系统是一次又一次的实现，系统本身对于在线学习是有用的。我从这个设计中获益良多，论文的编写需要有自己的意愿去实现一点，学习生活中所有的问题的勇气，学习的过程就是学习的过程。毕业设计，我学会了将理论知识应用于实践。让我知道该怎么做，我们必须认真对待。勇于克服困难，相信未来，我会做得更好。
参考文献
[1]Sufyan bin Uzayr. Conquering JavaScript:Node.js[M].CRC Press:2023-02-28.
[2]Paul Krill. Deno 1.30 backs built-in Node.js modules[J]. InfoWorld.com,2023.
[3]王婷.数字化背景下景区智慧旅游景点分享网站游客使用意愿影响机制研究[J].旅游纵览,2023(01):35-39.
[4]Yeager Emily,Boley B. Bynum,Goetcheus Cari. Conceptualizing peer-to-peer accommodations as disruptions in the urban tourism system[J]. Journal of Sustainable Tourism,2023,31(2).
[5]Dudley Katie D.,Duffy Lauren N.,Terry William C.,Norman William C.. Situational analysis as a critical methodology: mapping the tourism system in post-Katrina New Orleans[J]. Journal of Sustainable Tourism,2022,30(12).
[6]Matthew Tyson. Hands-on with MongoDB queryable encryption and Node.js[J]. InfoWorld.com,2022.
[7]Martin Heller. What is Node.js? The JavaScript runtime explained[J]. InfoWorld.com,2022.
[8]Khalilzadeh Jalayer. It is a small world, or is it? A look into two decades of tourism system[J]. Physica A: Statistical Mechanics and its Applications,2022,606.
[9]闵亮,薛格格,张玉欣,赵彩.基于Node.JS博客系统的设计与实现[J].电子设计工程,2022,30(07):37-41.DOI:10.14022/j.issn1674-6236.2022.07.008.
[10]韩增林,潘佳玉,郭建科,阴曙升.基于地理本性的滨海城市旅游景点分享网站适应性分析[J].资源科学,2022,44(03):634-645.
[11]李志敏. 基于数字文化旅游景点分享网站的推荐算法研究[D].青海师范大学,2022.DOI:10.27778/d.cnki.gqhzy.2022.000223.
[12]洪潜.数字经济时代重庆智慧旅游景点分享网站框架初探[J].西部旅游,2022(04):27-29.
[13]朱君,赵梓同.基于Node.js的旅游资源可视化构建平台设计与实现[J].电子技术与软件工程,2022(03):62-66.
[14]陈明雪,赵勇,周小丽,邓思风.基于Node.js和Bootstrap的图书设计与研究[J].现代信息科技,2021,5(24):12-15.DOI:10.19850/j.cnki.2096-4706.2021.24.004.
[15]袁文光.一种基于Node.js的校园高并发Web应用架构[J].南通职业大学学报,2021,35(04):77-81.
[16]吴有进.乡村旅游景点分享网站多元利益主体协同治理机制研究[J].农业经济,2021(12):58-59.
[17]余任杰,王风硕.基于Node.js的网上图书销售系统设计[J].电脑知识与技术,2021,17(34):83-84+92.DOI:10.14004/j.cnki.ckt.2021.3680.
[18]吴泳,黄天勇,闻平.基于Cesium的虚拟旅游景点分享网站研究[J].地理空间信息,2021,19(11):155-157+10.
[19]梁钰旎,陈莹,吕学静,贾文豪,莫伟鹏,雷渊.5G+VR环境模拟旅游景点分享网站设计[J].无线互联科技,2021,18(22):54-57.
[20] Ma Yanbin. Design of a competition answering platform based on Node.js and Vue framework [C] //. Proceedings of the 2021 Academic Annual Conference of the China Journalism and Technology Workers Federation., 2021: 77-82. DOI: 10.26914 /c.cnkihy.2021.047236.
[21] Yan Juan. English speaking test platform based on Node.js [J]. Microcomputer Applications, 2021, 37(08): 173-175.
[22] Fan Weiwei. A brief analysis of the information construction of archives management of tourist attractions sharing websites [J]. Office Business, 2021(12):106-107.
[23] Tang Bang. Research and implementation of Web server framework based on Node.js [D]. Southwest University of Science and Technology, 2021.DOI:10.27415/d.cnki.gxngc.2021.000946.
[24] Wang Huawei. Design and implementation of online bookstore based on Node.js[J]. China New Technologies and New Products, 2020(22):43-46.DOI:10.13612/j.cnki.cntp.2020.22.015.
[25] Mo Jing, Pei Darong. Implementation of tourist attraction sharing website based on WeChat applet [J]. Computer Programming Skills and Maintenance, 2020(07):55-57.DOI:10.16184/j.cnki.comprg.2020.07. 020.
Thanks
The completion of the tourist attraction sharing website and how to make it better require a lot of effort. This time will be unforgettable for a lifetime.
The tourist attraction sharing website can be completed smoothly. First of all, I would like to thank my instructor. He helped me in time when I encountered design problems and gave me sufficient guidance when I was confused about the design. With his help, I can complete a high-quality graduation project. During the development of the tourist attraction sharing website, the instructor put forward many practical opinions and suggestions, and provided me with a large amount of relevant research materials, which gave me a deeper understanding of the design. Only under the guidance of teachers can you achieve success in your graduation project. Here, I would like to express my deep gratitude to the instructor.
Here, I would also like to thank my classmates, who provided many reference opinions for my design and discussed design problems with me, so that my design matured step by step.
To get the project source code for free, please follow ❥ Like, collect and send a private message to the blogger, thank you~