073基於SSM酒店管理系統(前後臺)
技術:java+ssm+mysql+Navicat+tomcat+eclipse
截圖:
資料庫表:
CREATE TABLE account
(
id
int(11) NOT NULL AUTO_INCREMENT,
name
varchar(32) NOT NULL,
password
varchar(32) NOT NULL,
realName
varchar(32) DEFAULT NULL,
idCard
varchar(32) CHARACTER SET utf32 DEFAULT NULL,
mobile
varchar(16) DEFAULT NULL,
address
varchar(128) DEFAULT NULL,
status
int(1) DEFAULT ‘0’,
PRIMARY KEY (id
)
) ENGINE=InnoDB AUTO_INCREMENT=9 DEFAULT CHARSET=utf8;
– Records of account
INSERT INTO account
VALUES (‘1’, ‘李四’, ‘123456’, ‘李四’, ‘62225225666552’, ‘13656565656’, ‘上海 浦東’, ‘0’);
INSERT INTO account
VALUES (‘2’, ‘張三’, ‘123’, ‘張三五’, ‘4622987745565656’, ‘13912233333’, ‘北京 三里屯 酒吧’, ‘0’);
INSERT INTO account
VALUES (‘3’, ‘李四1’, ‘123’, ‘李四1’, ‘6565656565656’, ‘13999999999’, ‘南京’, ‘0’);
INSERT INTO account
VALUES (‘4’, ‘王麻子’, ‘123’, ‘大刀王五’, ‘110110120121110110’, ‘13656565656’, ‘北京 朝陽區 群眾’, ‘-1’);
INSERT INTO account
VALUES (‘5’, ‘小明’, ‘123456’, ‘張小明’, ‘31012002522555’, ‘13545455454’, ‘江蘇 南京’, ‘0’);
INSERT INTO account
VALUES (‘6’, ‘xia’, ‘123456’, null, null, ‘17615042024’, null, ‘0’);
INSERT INTO account
VALUES (‘7’, ‘李勝’, ‘123456’, ‘李勝’, null, ‘17615042024’, null, ‘0’);
INSERT INTO account
VALUES (‘8’, ‘zhangmaowen’, ‘123456’, ‘張茂’, ‘3412223234780’, ‘17615042024’, ‘大連’, ‘0’);
– Table structure for authority
DROP TABLE IF EXISTS authority
;
CREATE TABLE authority
(
id
int(11) NOT NULL AUTO_INCREMENT,
roleId
int(11) NOT NULL,
menuId
int(11) NOT NULL,
PRIMARY KEY (id
),
KEY roleId
(roleId
),
KEY menuId
(menuId
),
CONSTRAINT authority_ibfk_1
FOREIGN KEY (roleId
) REFERENCES role
(id
),
CONSTRAINT authority_ibfk_2
FOREIGN KEY (menuId
) REFERENCES menu
(id
)
) ENGINE=InnoDB AUTO_INCREMENT=437 DEFAULT CHARSET=utf8;
– Records of authority
INSERT INTO authority
VALUES (‘148’, ‘2’, ‘35’);
INSERT INTO authority
VALUES (‘149’, ‘2’, ‘36’);
INSERT INTO authority
VALUES (‘150’, ‘2’, ‘25’);
INSERT INTO authority
VALUES (‘151’, ‘2’, ‘1’);
INSERT INTO authority
VALUES (‘152’, ‘2’, ‘14’);
INSERT INTO authority
VALUES (‘153’, ‘2’, ‘15’);
INSERT INTO authority
VALUES (‘383’, ‘1’, ‘1’);
INSERT INTO authority
VALUES (‘384’, ‘1’, ‘5’);
INSERT INTO authority
VALUES (‘385’, ‘1’, ‘17’);
INSERT INTO authority
VALUES (‘386’, ‘1’, ‘18’);
INSERT INTO authority
VALUES (‘387’, ‘1’, ‘19’);
INSERT INTO authority
VALUES (‘388’, ‘1’, ‘20’);
INSERT INTO authority
VALUES (‘389’, ‘1’, ‘13’);
INSERT INTO authority
VALUES (‘390’, ‘1’, ‘21’);
INSERT INTO authority
VALUES (‘391’, ‘1’, ‘22’);
INSERT INTO authority
VALUES (‘392’, ‘1’, ‘23’);
INSERT INTO authority
VALUES (‘393’, ‘1’, ‘35’);
INSERT INTO authority
VALUES (‘394’, ‘1’, ‘36’);
INSERT INTO authority
VALUES (‘395’, ‘1’, ‘14’);
INSERT INTO authority
VALUES (‘396’, ‘1’, ‘15’);
INSERT INTO authority
VALUES (‘397’, ‘1’, ‘24’);
INSERT INTO authority
VALUES (‘398’, ‘1’, ‘25’);
INSERT INTO authority
VALUES (‘399’, ‘1’, ‘26’);
INSERT INTO authority
VALUES (‘400’, ‘1’, ‘31’);
INSERT INTO authority
VALUES (‘401’, ‘1’, ‘32’);
INSERT INTO authority
VALUES (‘402’, ‘1’, ‘33’);
INSERT INTO authority
VALUES (‘403’, ‘1’, ‘34’);
INSERT INTO authority
VALUES (‘404’, ‘1’, ‘37’);
INSERT INTO authority
VALUES (‘405’, ‘1’, ‘38’);
INSERT INTO authority
VALUES (‘406’, ‘1’, ‘39’);
INSERT INTO authority
VALUES (‘407’, ‘1’, ‘40’);
INSERT INTO authority
VALUES (‘408’, ‘1’, ‘41’);
INSERT INTO authority
VALUES (‘409’, ‘1’, ‘42’);
INSERT INTO authority
VALUES (‘410’, ‘1’, ‘43’);
INSERT INTO authority
VALUES (‘411’, ‘1’, ‘44’);
INSERT INTO authority
VALUES (‘412’, ‘1’, ‘45’);
INSERT INTO authority
VALUES (‘413’, ‘1’, ‘46’);
INSERT INTO authority
VALUES (‘414’, ‘1’, ‘47’);
INSERT INTO authority
VALUES (‘415’, ‘1’, ‘48’);
INSERT INTO authority
VALUES (‘416’, ‘1’, ‘49’);
INSERT INTO authority
VALUES (‘417’, ‘1’, ‘50’);
INSERT INTO authority
VALUES (‘418’, ‘1’, ‘51’);
INSERT INTO authority
VALUES (‘419’, ‘1’, ‘52’);
INSERT INTO authority
VALUES (‘420’, ‘1’, ‘53’);
INSERT INTO authority
VALUES (‘421’, ‘1’, ‘54’);
INSERT INTO authority
VALUES (‘422’, ‘1’, ‘55’);
INSERT INTO authority
VALUES (‘423’, ‘1’, ‘56’);
INSERT INTO authority
VALUES (‘424’, ‘1’, ‘57’);
INSERT INTO authority
VALUES (‘425’, ‘1’, ‘58’);
INSERT INTO authority
VALUES (‘426’, ‘1’, ‘59’);
INSERT INTO authority
VALUES (‘427’, ‘1’, ‘60’);
INSERT INTO authority
VALUES (‘428’, ‘1’, ‘61’);
INSERT INTO authority
VALUES (‘429’, ‘1’, ‘62’);
INSERT INTO authority
VALUES (‘430’, ‘1’, ‘63’);
INSERT INTO authority
VALUES (‘431’, ‘1’, ‘64’);
INSERT INTO authority
VALUES (‘432’, ‘1’, ‘65’);
INSERT INTO authority
VALUES (‘433’, ‘1’, ‘66’);
INSERT INTO authority
VALUES (‘434’, ‘1’, ‘67’);
INSERT INTO authority
VALUES (‘435’, ‘1’, ‘68’);
INSERT INTO authority
VALUES (‘436’, ‘1’, ‘69’);
– Table structure for book_order
DROP TABLE IF EXISTS book_order
;
CREATE TABLE book_order
(
id
int(11) NOT NULL AUTO_INCREMENT,
accountId
int(11) NOT NULL,
roomTypeId
int(11) NOT NULL,
name
varchar(32) NOT NULL,
idCard
varchar(32) CHARACTER SET utf32 DEFAULT NULL,
mobile
varchar(16) DEFAULT NULL,
status
int(1) DEFAULT ‘0’,
arriveDate
varchar(32) DEFAULT NULL,
leaveDate
varchar(32) NOT NULL,
remark
varchar(128) DEFAULT NULL,
createTime
datetime NOT NULL,
price
varchar(32) DEFAULT NULL,
yajin
varchar(32) DEFAULT NULL,
PRIMARY KEY (id
),
KEY accountId
(accountId
),
KEY roomTypeId
(roomTypeId
),
CONSTRAINT book_order_ibfk_1
FOREIGN KEY (accountId
) REFERENCES account
(id
),
CONSTRAINT book_order_ibfk_2
FOREIGN KEY (roomTypeId
) REFERENCES room_type
(id
)
) ENGINE=InnoDB AUTO_INCREMENT=29 DEFAULT CHARSET=utf8;
– Records of book_order
INSERT INTO book_order
VALUES (‘10’, ‘1’, ‘1’, ‘123’, ‘62225225666552’, ‘13656565656’, ‘2’, ‘2019-01-18’, ‘2019-01-19’, ‘da’, ‘2019-01-18 23:56:58’, null, null);
INSERT INTO book_order
VALUES (‘11’, ‘2’, ‘2’, ‘張三五’, ‘622987745565656’, ‘13918655256’, ‘2’, ‘2019-01-18’, ‘2019-01-19’, ‘’, ‘2019-01-18 23:57:11’, null, null);
INSERT INTO book_order
VALUES (‘13’, ‘3’, ‘1’, ‘李四’, ‘6565656565656’, ‘13999999999’, ‘0’, ‘2019-01-19’, ‘2019-01-20’, ‘預計晚上八點到。’, ‘2019-01-19 13:27:35’, null, null);
INSERT INTO book_order
VALUES (‘14’, ‘5’, ‘2’, ‘小明’, ‘31012002522555’, ‘13545455454’, ‘2’, ‘2019-01-19’, ‘2019-01-20’, ‘幫我留一個有窗戶的靠南的!謝謝!’, ‘2019-01-19 23:02:16’, null, null);
INSERT INTO book_order
VALUES (‘15’, ‘5’, ‘6’, ‘小明’, ‘31012002522555’, ‘13545455454’, ‘2’, ‘2019-01-21’, ‘2019-01-22’, ‘我會盡快趕來!’, ‘2019-01-19 23:02:45’, null, null);
INSERT INTO book_order
VALUES (‘16’, ‘5’, ‘10’, ‘小明’, ‘31012002522555’, ‘13545455454’, ‘1’, ‘2019-01-21’, ‘2019-01-23’, ‘奢侈一把!’, ‘2019-01-19 23:03:25’, null, null);
INSERT INTO book_order
VALUES (‘17’, ‘2’, ‘1’, ‘張三’, ‘4622987745565656’, ‘13912233333’, ‘2’, ‘2019-06-05’, ‘2019-06-06’, ‘好’, ‘2019-06-06 09:12:42’, null, null);
INSERT INTO book_order
VALUES (‘18’, ‘7’, ‘11’, ‘李勝’, ‘3412223234780’, ‘17615042024’, ‘1’, ‘2019-06-10’, ‘2019-06-11’, ‘你好’, ‘2019-06-10 08:17:32’, null, null);
INSERT INTO book_order
VALUES (‘19’, ‘6’, ‘1’, ‘xia’, ‘341222199907208452’, ‘17615042024’, ‘0’, ‘2019-06-17’, ‘2019-06-19’, ‘大家好’, ‘2019-06-18 12:10:39’, null, null);
INSERT INTO book_order
VALUES (‘20’, ‘6’, ‘12’, ‘黎華’, ‘233256654’, ‘17615042024’, ‘1’, ‘2019-06-19’, ‘2019-06-20’, ‘’, ‘2019-06-19 00:39:16’, null, null);
INSERT INTO book_order
VALUES (‘21’, ‘6’, ‘1’, ‘夏天’, ‘23233232’, ‘17615042024’, ‘0’, ‘2019-06-18’, ‘2019-06-20’, ‘23232’, ‘2019-06-19 20:07:53’, null, null);
INSERT INTO book_order
VALUES (‘22’, ‘6’, ‘1’, ‘LI’, ‘1213’, ‘17615042024’, ‘0’, ‘2019-06-17’, ‘2019-06-20’, ‘12121’, ‘2019-06-19 20:32:54’, null, null);
INSERT INTO book_order
VALUES (‘23’, ‘6’, ‘1’, ‘MAHANG’, ‘12’, ‘17615042024’, ‘1’, ‘2019-06-15’, ‘2019-06-20’, ‘12’, ‘2019-06-19 21:01:11’, ‘495’, ‘100’);
INSERT INTO book_order
VALUES (‘24’, ‘6’, ‘2’, ‘李生’, ‘343434’, ‘17615042024’, ‘1’, ‘2019-06-19’, ‘2019-06-21’, ‘33434’, ‘2019-06-19 21:52:33’, ‘598’, ‘200’);
INSERT INTO book_order
VALUES (‘25’, ‘6’, ‘1’, ‘麗水’, ‘12’, ‘17615042024’, ‘2’, ‘2019-06-19’, ‘2019-06-27’, ‘2313’, ‘2019-06-19 22:06:50’, ‘792’, ‘100’);
INSERT INTO book_order
VALUES (‘26’, ‘6’, ‘1’, ‘xia’, ‘34568791’, ‘17615042024’, ‘0’, ‘2019-09-10’, ‘2019-09-12’, ‘1’, ‘2019-09-11 10:45:54’, ‘198’, ‘100’);
INSERT INTO book_order
VALUES (‘27’, ‘6’, ‘2’, ‘xia’, ‘11’, ‘17615042024’, ‘0’, ‘2019-09-11’, ‘2019-09-13’, ‘1111’, ‘2019-09-11 10:53:45’, ‘598’, ‘200’);
INSERT INTO book_order
VALUES (‘28’, ‘6’, ‘1’, ‘xia’, ‘11’, ‘17615042024’, ‘0’, ‘2019-09-25’, ‘2019-09-26’, ‘11’, ‘2019-09-25 16:13:54’, ‘99’, ‘100’);
原始碼下載:http://www.bycxy123.com/
視訊演示:https://www.bilibili.com/video/BV1K7411a7i6/
相關文章
- ssm星級酒店管理系統SSM
- 基於SSM的酒店管理系統畢業設計論文【範文】SSM
- 基於 ThinkPHP6 開發的模組化前後臺分離管理系統PHP
- 基於 Hyperf 開發的前後分離管理後臺
- Catchadmin 基於 Tp6 的 前後端分離後臺管理許可權系統後端
- 基於adminlte的後臺管理系統開發
- 基於SSM開發的物業維修管理系統SSM
- Java SSM練手小專案-手把手帶你搭建一個基於SSM框架的人力資源管理後臺系統JavaSSM框架
- 基於SpringCloud+vue(ElementUI)+mySQL前後端分離設計之–搭建後臺管理系統SpringGCCloudVueUIMySql後端
- 基於vite2+electron12後臺管理模板|Electron後臺框架系統Vite框架
- EacooPHP基於ThinkPHP5+AdminLTE後臺管理系統OOPPHP
- guns Lite基於spring boot的後臺管理系統Spring Boot
- 基於SSM框架的JavaWeb通用許可權管理系統SSM框架JavaWeb
- 基於SSM開發的企業人事管理系統SSM
- 基於SSM開發的健身俱樂部管理系統 JAVA MySQLSSMJavaMySql
- 基於SSM框架的文章管理系統(增加留言回覆功能)SSM框架
- 前端完全基於Layui的LarryMS後臺管理模板,後臺完全基於ThinkPHP5.x的LarryCMS內容管理系統前端UIPHP
- 基於Vue + Antd 搭建自己的部落格後臺管理系統Vue
- 基於angular7的多頁面後臺管理系統Angular
- 基於Vue和Node.js的電商後臺管理系統VueNode.js
- 基於easyui 1.3.6設計的後臺管理系統模板介面UI
- 基於nuxt和iview搭建後臺管理系統實踐(1)UXView
- 基於 hyperf,vuetify,casbin 開發的前後端分離管理系統Vue後端
- 基於SSM的職員考勤系統SSM
- pms酒店管理系統功能,酒店管理系統軟體開發
- 基於Hyperf + Vue + Element 構建的後臺管理系統(內建聊天系統)Vue
- 後臺管理系統
- 基於 Thinkphp 6 + Vue2 的,一鍵生成程式碼的,前後端分離的,後臺管理系統PHPVue後端
- 基於 vue-element-admin 高效開發後臺管理系統Vue
- 基於 Nuxt.js 服務渲染框架的後臺管理系統UXJS框架
- 分享一套基於bootstrap的後臺管理系統html模板bootHTML
- yamecent-admin 基於 Laravel 框架的 rbac 後臺管理系統Laravel框架
- 基於Laravel5.8實現的元件化後臺管理系統Laravel元件化
- 基於vue2.0 +vuex+ element-ui後臺管理系統VueUI
- Java基於SSM框架的計算機學院管理系統(3)JavaSSM框架計算機
- 基於ssm、Vue.js的簡單教師資訊管理系統SSMVue.js
- java 基於SSM框架開發線上音樂視訊MV管理系統JavaSSM框架
- SSM-框架搭建-tank後臺學習系統SSM框架