zbpt/db/20190311_zxy_sensitive_word.sql
小黄狗横扫士力架 bfc6a73c2f first commit
2022-12-28 09:45:16 +08:00

44 lines
1.6 KiB
SQL
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/*
Navicat MySQL Data Transfer
Source Server : DB
Source Server Version : 80011
Source Host : localhost:3306
Source Database : aijinan
Target Server Type : MYSQL
Target Server Version : 80011
File Encoding : 65001
Date: 2019-03-11 17:48:09
*/
SET FOREIGN_KEY_CHECKS=0;
-- ----------------------------
-- Table structure for sensitive_stop_word
-- ----------------------------
DROP TABLE IF EXISTS `sensitive_stop_word`;
CREATE TABLE `sensitive_stop_word` (
`id` int(11) NOT NULL AUTO_INCREMENT COMMENT '停顿符id',
`stop_word` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL COMMENT '停顿符',
`create_by` bigint(20) NOT NULL COMMENT '创建者id',
`create_time` timestamp NOT NULL COMMENT '创建时间',
`is_delete` tinyint(4) NOT NULL DEFAULT '0' COMMENT '是否删除默认为0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin COMMENT='敏感停顿符';
-- ----------------------------
-- Table structure for sensitive_word
-- ----------------------------
DROP TABLE IF EXISTS `sensitive_word`;
CREATE TABLE `sensitive_word` (
`id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'id',
`sensitive_word` varchar(255) COLLATE utf8mb4_bin NOT NULL COMMENT '敏感词',
`replace_word` varchar(255) COLLATE utf8mb4_bin DEFAULT NULL COMMENT '替换词',
`create_by` bigint(20) NOT NULL COMMENT '创建者id',
`create_time` timestamp NOT NULL COMMENT '创建时间',
`is_delete` tinyint(4) NOT NULL DEFAULT '0' COMMENT '是否删除默认为0不删除',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin COMMENT='敏感词';