https://hub.docker.com/r/hhyo/archery
https://github.com/hhyo/archery/
https://hub.docker.com/r/hanchuanchuan/goinception
https://hub.docker.com/r/hhyo/inception
https://github.com/hanchuanchuan/goInception
https://inception-document.readthedocs.io/zh_CN/latest/
https://hanchuanchuan.github.io/goInception/
---goinception
-审核、执行、备份于一身的MySQL运维工具
docker run -d --name goinception --restart always -p 4000:4000 --privileged=true --user=root -e TZ='Asia/Shanghai' --ulimit nofile=262144:262144 -v /etc/localtime:/etc/localtime:ro --network mgr --ip 172.18.0.61 -v /data/site/docker/env/bizdata/archery/inception/config.toml:/etc/config.toml:rw hanchuanchuan/goinception
---archery
-SQL审核查询平台
docker run -d --name archery --hostname=archery -p 9123:9123 --restart=always --privileged=true --user=root -e TZ='Asia/Shanghai' --ulimit nofile=262144:262144 -v /etc/localtime:/etc/localtime:ro \ -e Q_CLUISTER_WORKERS='4' -e CSRF_TRUSTED_ORIGINS='http://127.0.0.1:9123' \ -e DATABASE_URL='mysql://opt:WdqOpt@172.18.0.6:3306/htmltooarchery' \ -e NGINX_PORT='9123' \ -e AUTH_LDAP_USER_ATTR_MAP='username=cn,display=displayname,email=email' \ -e DEBUG='false' -e AUTH_LDAP_ALWAYS_UPDATE_USER='true' \ -e ENABLE_LDAP='false' \ -e CACHE_URL='redis://172.18.0.79:6379/15?PASSWORD=wdqdmm@r' \ -e Q_CLUISTER_TIMEOUT='60' -e Q_CLUISTER_SYNC='false' \ -v /data/site/docker/env/bizdata/archery/archery/settings.py:/opt/archery/local_settings.py:rw \ -v /data/site/docker/env/bizdata/archery/archery/soar.yaml:/etc/soar.yaml:rw \ -v /data/site/docker/env/bizdata/archery/archery/docs.md:/opt/archery/docs/docs.md:rw \ -v /data/site/docker/env/bizdata/archery/archery/downloads:/opt/archery/downloads:rw \ -v /data/site/docker/env/bizdata/archery/archery/sql/migrations:/opt/archery/sql/migrations:rw \ -v /data/site/docker/env/bizdata/archery/archery/logs:/opt/archery/logs:rw \ -v /data/site/docker/env/bizdata/archery/archery/keys:/opt/archery/keys:rw \ -v /data/site/docker/env/bizdata/archery/.env:/opt/archery/.env:ro \ -v /data/site/docker/env/bizdata/archery/templates/common:/opt/archery/common/templates:ro \ --workdir=/opt/archery hhyo/archery:v1.11.1
docker exec -ti archery /bin/bash
# 功能清单
| 数据库 | 查询 | 审核 | 执行 | 备份 | 数据字典 | 慢日志 | 会话管理 | 账号管理 | 参数管理 | 数据归档 |
|---|---|---|---|---|---|---|---|---|---|---|
| MySQL | √ | √ | √ | √ | √ | √ | √ | √ | √ | √ |
| MsSQL | √ | × | √ | × | √ | × | × | × | × | × |
| Redis | √ | × | √ | × | × | × | × | × | × | × |
| PgSQL | √ | × | √ | × | × | × | × | × | × | × |
| Oracle | √ | √ | √ | √ | √ | × | × | × | × | × |
| MongoDB | √ | √ | √ | × | × | × | × | × | × | × |
| Phoenix | √ | × | √ | × | × | × | × | × | × | × |
| ODPS | √ | × | × | × | × | × | × | × | × | × |
| ClickHouse | √ | √ | √ | × | × | × | × | × | × | × |
# 初始化
cd /data/site/htmltoo.opt/
wget https://github.com/hhyo/Archery/archive/refs/tags/v1.11.1.zip
unzip v1.11.1.zip
cd Archery-1.11.1/src/docker-compose
docker-compose -f docker-compose.yml up -d
docker exec -ti archery /bin/bash
cd /opt/archery
source /opt/venv4archery/bin/activate
python3 manage.py makemigrations sql
python3 manage.py migrate
#数据初始化
python3 manage.py dbshell<sql/fixtures/auth_group.sql
python3 manage.py dbshell<src/init_sql/mysql_slow_query_review.sql
#创建管理用户
python3 manage.py createsuperuser
#重启服务
docker restart archery
#日志查看和问题排查
docker logs archery -f --tail=10
logs/archery.log
docker commit -m="update" -a="htmltoo.com" archery hub.htmltoo.com:5000/db:archery-1.11.1
docker push hub.htmltoo.com:5000/db:archery-1.11.1
docker save hub.htmltoo.com:5000/db:archery-1.11.1 | gzip > /data/site/htmltoo.f/htmltoo.up/soft/docker.tar/archery-1.11.1.tar.gz
# load - 镜像解压
docker load < /opt/archery-1.11.1.tar.gz
---sql
-- --------------------------------------------------------
-- 主机: g.htmltoo.com
-- 服务器版本: 8.0.35 - MySQL Community Server - GPL
-- 服务器操作系统: Linux
-- HeidiSQL 版本: 12.6.0.6770
-- --------------------------------------------------------
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET NAMES utf8 */;
/*!50503 SET NAMES utf8mb4 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
-- 导出 htmltooarchery 的数据库结构
DROP DATABASE IF EXISTS `htmltooarchery`;
CREATE DATABASE IF NOT EXISTS `htmltooarchery` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci */ /*!80016 DEFAULT ENCRYPTION='N' */;
USE `htmltooarchery`;
-- 导出 表 htmltooarchery.2fa_config 结构
DROP TABLE IF EXISTS `2fa_config`;
CREATE TABLE IF NOT EXISTS `2fa_config` (
`id` int NOT NULL AUTO_INCREMENT,
`username` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`auth_type` varchar(128) COLLATE utf8mb4_general_ci NOT NULL,
`phone` varchar(64) COLLATE utf8mb4_general_ci DEFAULT NULL,
`secret_key` varchar(256) COLLATE utf8mb4_general_ci DEFAULT NULL,
`user_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `2fa_config_user_id_auth_type_303171fc_uniq` (`user_id`,`auth_type`),
CONSTRAINT `2fa_config_user_id_a0d1d7c2_fk_sql_users_id` FOREIGN KEY (`user_id`) REFERENCES `sql_users` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.2fa_config 的数据：~0 rows (大约)
DELETE FROM `2fa_config`;
INSERT INTO `2fa_config` (`id`, `username`, `auth_type`, `phone`, `secret_key`, `user_id`) VALUES
(1, 'tzxlKzuTvWfk-1HLCT_guw==', 'pkCs0opPk_Z8Z6U8NMlWAA==', 'BnJSUXJxlgf5K8lnvoXrLg==', 'Obnyqcv4fatRwDmKnSbXhDXQrnBYEvw84MINsrUfBIsGclJRcnGWB_kryWe-hesu', 1);
-- 导出 表 htmltooarchery.aliyun_rds_config 结构
DROP TABLE IF EXISTS `aliyun_rds_config`;
CREATE TABLE IF NOT EXISTS `aliyun_rds_config` (
`id` int NOT NULL AUTO_INCREMENT,
`rds_dbinstanceid` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`is_enable` tinyint(1) NOT NULL,
`ak_id` int NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `instance_id` (`instance_id`),
KEY `aliyun_rds_config_ak_id_d150152f_fk_cloud_access_key_id` (`ak_id`),
CONSTRAINT `aliyun_rds_config_ak_id_d150152f_fk_cloud_access_key_id` FOREIGN KEY (`ak_id`) REFERENCES `cloud_access_key` (`id`),
CONSTRAINT `aliyun_rds_config_instance_id_4ad756cc_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.aliyun_rds_config 的数据：~0 rows (大约)
DELETE FROM `aliyun_rds_config`;
-- 导出 表 htmltooarchery.archive_config 结构
DROP TABLE IF EXISTS `archive_config`;
CREATE TABLE IF NOT EXISTS `archive_config` (
`id` int NOT NULL AUTO_INCREMENT,
`title` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`audit_auth_groups` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`src_db_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`src_table_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`dest_db_name` varchar(64) COLLATE utf8mb4_general_ci DEFAULT NULL,
`dest_table_name` varchar(64) COLLATE utf8mb4_general_ci DEFAULT NULL,
`condition` varchar(1000) COLLATE utf8mb4_general_ci NOT NULL,
`mode` varchar(10) COLLATE utf8mb4_general_ci NOT NULL,
`no_delete` tinyint(1) NOT NULL,
`sleep` int NOT NULL,
`status` int NOT NULL,
`state` tinyint(1) NOT NULL,
`user_name` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`last_archive_time` datetime(6) DEFAULT NULL,
`sys_time` datetime(6) NOT NULL,
`dest_instance_id` int DEFAULT NULL,
`resource_group_id` int NOT NULL,
`src_instance_id` int NOT NULL,
PRIMARY KEY (`id`),
KEY `archive_config_dest_instance_id_0806c7bb_fk_sql_instance_id` (`dest_instance_id`),
KEY `archive_config_resource_group_id_f39b0042_fk_resource_` (`resource_group_id`),
KEY `archive_config_src_instance_id_4dd96d4d_fk_sql_instance_id` (`src_instance_id`),
CONSTRAINT `archive_config_dest_instance_id_0806c7bb_fk_sql_instance_id` FOREIGN KEY (`dest_instance_id`) REFERENCES `sql_instance` (`id`),
CONSTRAINT `archive_config_resource_group_id_f39b0042_fk_resource_` FOREIGN KEY (`resource_group_id`) REFERENCES `resource_group` (`group_id`),
CONSTRAINT `archive_config_src_instance_id_4dd96d4d_fk_sql_instance_id` FOREIGN KEY (`src_instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.archive_config 的数据：~0 rows (大约)
DELETE FROM `archive_config`;
-- 导出 表 htmltooarchery.archive_log 结构
DROP TABLE IF EXISTS `archive_log`;
CREATE TABLE IF NOT EXISTS `archive_log` (
`id` int NOT NULL AUTO_INCREMENT,
`cmd` varchar(2000) COLLATE utf8mb4_general_ci NOT NULL,
`condition` varchar(1000) COLLATE utf8mb4_general_ci NOT NULL,
`mode` varchar(10) COLLATE utf8mb4_general_ci NOT NULL,
`no_delete` tinyint(1) NOT NULL,
`sleep` int NOT NULL,
`select_cnt` int NOT NULL,
`insert_cnt` int NOT NULL,
`delete_cnt` int NOT NULL,
`statistics` longtext COLLATE utf8mb4_general_ci NOT NULL,
`success` tinyint(1) NOT NULL,
`error_info` longtext COLLATE utf8mb4_general_ci NOT NULL,
`start_time` datetime(6) NOT NULL,
`end_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
`archive_id` int NOT NULL,
PRIMARY KEY (`id`),
KEY `archive_log_archive_id_e35eacdf_fk_archive_config_id` (`archive_id`),
CONSTRAINT `archive_log_archive_id_e35eacdf_fk_archive_config_id` FOREIGN KEY (`archive_id`) REFERENCES `archive_config` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.archive_log 的数据：~0 rows (大约)
DELETE FROM `archive_log`;
-- 导出 表 htmltooarchery.audit_log 结构
DROP TABLE IF EXISTS `audit_log`;
CREATE TABLE IF NOT EXISTS `audit_log` (
`id` int NOT NULL AUTO_INCREMENT,
`user_id` int NOT NULL,
`user_name` varchar(30) COLLATE utf8mb4_general_ci DEFAULT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci DEFAULT NULL,
`action` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`extra_info` longtext COLLATE utf8mb4_general_ci,
`action_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.audit_log 的数据：~0 rows (大约)
DELETE FROM `audit_log`;
INSERT INTO `audit_log` (`id`, `user_id`, `user_name`, `user_display`, `action`, `extra_info`, `action_time`) VALUES
(1, 1, 'ihunter', '', '登入失败', NULL, '2023-11-14 13:10:12.849810'),
(2, 1, 'ihunter', '', '登入失败', NULL, '2023-11-14 13:10:23.805483'),
(3, 1, 'ihunter', '', '登入', '172.17.0.1', '2023-11-14 13:10:39.855027'),
(4, 1, 'ihunter', '', '登出', '172.17.0.1', '2023-11-14 13:16:10.461552'),
(5, 1, 'ihunter', '', '登入', '172.17.0.1', '2023-11-14 13:16:20.090513'),
(6, 1, 'ihunter', '', '登出', '172.17.0.1', '2023-11-14 14:39:10.233142'),
(7, 1, 'ihunter', '', '登入', '172.17.0.1', '2023-11-14 14:40:15.002456'),
(8, 1, 'ihunter', '', '登出', '172.17.0.1', '2023-11-14 15:39:36.615657'),
(9, 1, 'ihunter', '', '登入失败', NULL, '2023-11-14 15:41:22.371442'),
(10, 1, 'ihunter', '', '登入', '172.17.0.1', '2023-11-14 15:41:58.503338');
-- 导出 表 htmltooarchery.auth_group 结构
DROP TABLE IF EXISTS `auth_group`;
CREATE TABLE IF NOT EXISTS `auth_group` (
`id` int NOT NULL AUTO_INCREMENT,
`name` varchar(150) COLLATE utf8mb4_general_ci NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `name` (`name`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.auth_group 的数据：~0 rows (大约)
DELETE FROM `auth_group`;
INSERT INTO `auth_group` (`id`, `name`) VALUES
(3, 'DBA'),
(1, 'Default'),
(4, 'PM'),
(5, 'QA'),
(2, 'RD');
-- 导出 表 htmltooarchery.auth_group_permissions 结构
DROP TABLE IF EXISTS `auth_group_permissions`;
CREATE TABLE IF NOT EXISTS `auth_group_permissions` (
`id` int NOT NULL AUTO_INCREMENT,
`group_id` int NOT NULL,
`permission_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `auth_group_permissions_group_id_permission_id_0cd325b0_uniq` (`group_id`,`permission_id`),
KEY `auth_group_permissio_permission_id_84c5c92e_fk_auth_perm` (`permission_id`),
CONSTRAINT `auth_group_permissio_permission_id_84c5c92e_fk_auth_perm` FOREIGN KEY (`permission_id`) REFERENCES `auth_permission` (`id`),
CONSTRAINT `auth_group_permissions_group_id_b120cbf9_fk_auth_group_id` FOREIGN KEY (`group_id`) REFERENCES `auth_group` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=148 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.auth_group_permissions 的数据：~0 rows (大约)
DELETE FROM `auth_group_permissions`;
INSERT INTO `auth_group_permissions` (`id`, `group_id`, `permission_id`) VALUES
(5, 1, 83),
(2, 1, 85),
(4, 1, 86),
(3, 1, 87),
(1, 1, 103),
(10, 2, 81),
(18, 2, 82),
(21, 2, 83),
(17, 2, 84),
(13, 2, 85),
(20, 2, 86),
(14, 2, 87),
(19, 2, 88),
(16, 2, 89),
(15, 2, 90),
(11, 2, 97),
(22, 2, 98),
(9, 2, 99),
(12, 2, 103),
(29, 2, 105),
(28, 2, 108),
(27, 2, 109),
(24, 2, 110),
(23, 2, 112),
(25, 2, 113),
(26, 2, 116),
(8, 2, 128),
(45, 3, 81),
(62, 3, 82),
(65, 3, 83),
(61, 3, 84),
(56, 3, 85),
(64, 3, 86),
(57, 3, 87),
(63, 3, 88),
(60, 3, 89),
(59, 3, 90),
(50, 3, 91),
(52, 3, 92),
(48, 3, 93),
(46, 3, 94),
(51, 3, 95),
(55, 3, 96),
(47, 3, 97),
(67, 3, 98),
(44, 3, 99),
(53, 3, 100),
(58, 3, 101),
(66, 3, 102),
(49, 3, 103),
(54, 3, 104),
(85, 3, 105),
(84, 3, 106),
(83, 3, 107),
(82, 3, 108),
(81, 3, 109),
(69, 3, 110),
(70, 3, 111),
(68, 3, 112),
(76, 3, 113),
(77, 3, 114),
(79, 3, 115),
(80, 3, 116),
(75, 3, 117),
(78, 3, 118),
(74, 3, 119),
(73, 3, 120),
(86, 3, 121),
(88, 3, 122),
(87, 3, 123),
(43, 3, 124),
(72, 3, 125),
(71, 3, 126),
(42, 3, 127),
(39, 3, 128),
(41, 3, 129),
(40, 3, 130),
(105, 4, 81),
(113, 4, 82),
(116, 4, 83),
(112, 4, 84),
(108, 4, 85),
(115, 4, 86),
(109, 4, 87),
(114, 4, 88),
(111, 4, 89),
(110, 4, 90),
(106, 4, 97),
(117, 4, 98),
(104, 4, 99),
(107, 4, 103),
(127, 4, 105),
(126, 4, 106),
(125, 4, 107),
(124, 4, 108),
(123, 4, 109),
(119, 4, 110),
(118, 4, 112),
(120, 4, 113),
(121, 4, 115),
(122, 4, 116),
(102, 4, 128),
(103, 4, 129),
(133, 5, 81),
(138, 5, 82),
(140, 5, 83),
(136, 5, 85),
(139, 5, 86),
(137, 5, 87),
(134, 5, 97),
(135, 5, 103),
(144, 5, 105),
(143, 5, 108),
(141, 5, 113),
(142, 5, 116);
-- 导出 表 htmltooarchery.auth_permission 结构
DROP TABLE IF EXISTS `auth_permission`;
CREATE TABLE IF NOT EXISTS `auth_permission` (
`id` int NOT NULL AUTO_INCREMENT,
`name` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`content_type_id` int NOT NULL,
`codename` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `auth_permission_content_type_id_codename_01ab375a_uniq` (`content_type_id`,`codename`),
CONSTRAINT `auth_permission_content_type_id_2f476e4b_fk_django_co` FOREIGN KEY (`content_type_id`) REFERENCES `django_content_type` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=213 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.auth_permission 的数据：~0 rows (大约)
DELETE FROM `auth_permission`;
INSERT INTO `auth_permission` (`id`, `name`, `content_type_id`, `codename`) VALUES
(1, 'Can add log entry', 1, 'add_logentry'),
(2, 'Can change log entry', 1, 'change_logentry'),
(3, 'Can delete log entry', 1, 'delete_logentry'),
(4, 'Can view log entry', 1, 'view_logentry'),
(5, 'Can add permission', 2, 'add_permission'),
(6, 'Can change permission', 2, 'change_permission'),
(7, 'Can delete permission', 2, 'delete_permission'),
(8, 'Can view permission', 2, 'view_permission'),
(9, 'Can add group', 3, 'add_group'),
(10, 'Can change group', 3, 'change_group'),
(11, 'Can delete group', 3, 'delete_group'),
(12, 'Can view group', 3, 'view_group'),
(13, 'Can add content type', 4, 'add_contenttype'),
(14, 'Can change content type', 4, 'change_contenttype'),
(15, 'Can delete content type', 4, 'delete_contenttype'),
(16, 'Can view content type', 4, 'view_contenttype'),
(17, 'Can add session', 5, 'add_session'),
(18, 'Can change session', 5, 'change_session'),
(19, 'Can delete session', 5, 'delete_session'),
(20, 'Can view session', 5, 'view_session'),
(21, 'Can add Scheduled task', 6, 'add_schedule'),
(22, 'Can change Scheduled task', 6, 'change_schedule'),
(23, 'Can delete Scheduled task', 6, 'delete_schedule'),
(24, 'Can view Scheduled task', 6, 'view_schedule'),
(25, 'Can add task', 7, 'add_task'),
(26, 'Can change task', 7, 'change_task'),
(27, 'Can delete task', 7, 'delete_task'),
(28, 'Can view task', 7, 'view_task'),
(29, 'Can add Failed task', 8, 'add_failure'),
(30, 'Can change Failed task', 8, 'change_failure'),
(31, 'Can delete Failed task', 8, 'delete_failure'),
(32, 'Can view Failed task', 8, 'view_failure'),
(33, 'Can add Successful task', 9, 'add_success'),
(34, 'Can change Successful task', 9, 'change_success'),
(35, 'Can delete Successful task', 9, 'delete_success'),
(36, 'Can view Successful task', 9, 'view_success'),
(37, 'Can add Queued task', 10, 'add_ormq'),
(38, 'Can change Queued task', 10, 'change_ormq'),
(39, 'Can delete Queued task', 10, 'delete_ormq'),
(40, 'Can view Queued task', 10, 'view_ormq'),
(41, 'Can add 慢日志统计', 11, 'add_slowquery'),
(42, 'Can change 慢日志统计', 11, 'change_slowquery'),
(43, 'Can delete 慢日志统计', 11, 'delete_slowquery'),
(44, 'Can view 慢日志统计', 11, 'view_slowquery'),
(45, 'Can add 慢日志明细', 12, 'add_slowqueryhistory'),
(46, 'Can change 慢日志明细', 12, 'change_slowqueryhistory'),
(47, 'Can delete 慢日志明细', 12, 'delete_slowqueryhistory'),
(48, 'Can view 慢日志明细', 12, 'view_slowqueryhistory'),
(49, 'Can add 归档配置表', 13, 'add_archiveconfig'),
(50, 'Can change 归档配置表', 13, 'change_archiveconfig'),
(51, 'Can delete 归档配置表', 13, 'delete_archiveconfig'),
(52, 'Can view 归档配置表', 13, 'view_archiveconfig'),
(53, 'Can add 审计日志', 14, 'add_auditentry'),
(54, 'Can change 审计日志', 14, 'change_auditentry'),
(55, 'Can delete 审计日志', 14, 'delete_auditentry'),
(56, 'Can view 审计日志', 14, 'view_auditentry'),
(57, 'Can add 云服务认证信息配置', 15, 'add_cloudaccesskey'),
(58, 'Can change 云服务认证信息配置', 15, 'change_cloudaccesskey'),
(59, 'Can delete 云服务认证信息配置', 15, 'delete_cloudaccesskey'),
(60, 'Can view 云服务认证信息配置', 15, 'view_cloudaccesskey'),
(61, 'Can add 系统配置', 16, 'add_config'),
(62, 'Can change 系统配置', 16, 'change_config'),
(63, 'Can delete 系统配置', 16, 'delete_config'),
(64, 'Can view 系统配置', 16, 'view_config'),
(65, 'Can add 脱敏规则配置', 17, 'add_datamaskingrules'),
(66, 'Can change 脱敏规则配置', 17, 'change_datamaskingrules'),
(67, 'Can delete 脱敏规则配置', 17, 'delete_datamaskingrules'),
(68, 'Can view 脱敏规则配置', 17, 'view_datamaskingrules'),
(69, 'Can add 实例配置', 18, 'add_instance'),
(70, 'Can change 实例配置', 18, 'change_instance'),
(71, 'Can delete 实例配置', 18, 'delete_instance'),
(72, 'Can view 实例配置', 18, 'view_instance'),
(73, 'Can add 实例标签', 19, 'add_instancetag'),
(74, 'Can change 实例标签', 19, 'change_instancetag'),
(75, 'Can delete 实例标签', 19, 'delete_instancetag'),
(76, 'Can view 实例标签', 19, 'view_instancetag'),
(77, 'Can add permission', 20, 'add_permission'),
(78, 'Can change permission', 20, 'change_permission'),
(79, 'Can delete permission', 20, 'delete_permission'),
(80, 'Can view permission', 20, 'view_permission'),
(81, '菜单 Dashboard', 20, 'menu_dashboard'),
(82, '菜单 SQL审核', 20, 'menu_sqlcheck'),
(83, '菜单 SQL上线', 20, 'menu_sqlworkflow'),
(84, '菜单 SQL分析', 20, 'menu_sqlanalyze'),
(85, '菜单 SQL查询', 20, 'menu_query'),
(86, '菜单 在线查询', 20, 'menu_sqlquery'),
(87, '菜单 权限管理', 20, 'menu_queryapplylist'),
(88, '菜单 SQL优化', 20, 'menu_sqloptimize'),
(89, '菜单 优化工具', 20, 'menu_sqladvisor'),
(90, '菜单 慢查日志', 20, 'menu_slowquery'),
(91, '菜单 实例管理', 20, 'menu_instance'),
(92, '菜单 实例列表', 20, 'menu_instance_list'),
(93, '菜单 会话管理', 20, 'menu_dbdiagnostic'),
(94, '菜单 数据库管理', 20, 'menu_database'),
(95, '菜单 实例账号管理', 20, 'menu_instance_account'),
(96, '菜单 参数配置', 20, 'menu_param'),
(97, '菜单 数据字典', 20, 'menu_data_dictionary'),
(98, '菜单 工具插件', 20, 'menu_tools'),
(99, '菜单 数据归档', 20, 'menu_archive'),
(100, '菜单 My2SQL', 20, 'menu_my2sql'),
(101, '菜单 SchemaSync', 20, 'menu_schemasync'),
(102, '菜单 系统管理', 20, 'menu_system'),
(103, '菜单 相关文档', 20, 'menu_document'),
(104, '菜单 OpenAPI', 20, 'menu_openapi'),
(105, '提交SQL上线工单', 20, 'sql_submit'),
(106, '审核SQL上线工单', 20, 'sql_review'),
(107, '执行SQL上线工单(资源组粒度)', 20, 'sql_execute_for_resource_group'),
(108, '执行SQL上线工单(仅自己提交的)', 20, 'sql_execute'),
(109, '执行SQL分析', 20, 'sql_analyze'),
(110, '执行SQLAdvisor', 20, 'optimize_sqladvisor'),
(111, '执行SQLTuning', 20, 'optimize_sqltuning'),
(112, '执行SOAR', 20, 'optimize_soar'),
(113, '申请查询权限', 20, 'query_applypriv'),
(114, '管理查询权限', 20, 'query_mgtpriv'),
(115, '审核查询权限', 20, 'query_review'),
(116, '提交SQL查询', 20, 'query_submit'),
(117, '可查询所有实例', 20, 'query_all_instances'),
(118, '可查询所在资源组内的所有实例', 20, 'query_resource_group_instance'),
(119, '查看会话', 20, 'process_view'),
(120, '终止会话', 20, 'process_kill'),
(121, '查看表空间', 20, 'tablespace_view'),
(122, '查看事务信息', 20, 'trx_view'),
(123, '查看锁信息', 20, 'trxandlocks_view'),
(124, '管理实例账号', 20, 'instance_account_manage'),
(125, '查看实例参数列表', 20, 'param_view'),
(126, '修改实例参数', 20, 'param_edit'),
(127, '导出数据字典', 20, 'data_dictionary_export'),
(128, '提交归档申请', 20, 'archive_apply'),
(129, '审核归档申请', 20, 'archive_review'),
(130, '管理归档申请', 20, 'archive_mgt'),
(131, '审计权限', 20, 'audit_user'),
(132, '在线查询下载权限', 20, 'query_download'),
(133, 'Can add 查询日志', 21, 'add_querylog'),
(134, 'Can change 查询日志', 21, 'change_querylog'),
(135, 'Can delete 查询日志', 21, 'delete_querylog'),
(136, 'Can view 查询日志', 21, 'view_querylog'),
(137, 'Can add 资源组管理', 22, 'add_resourcegroup'),
(138, 'Can change 资源组管理', 22, 'change_resourcegroup'),
(139, 'Can delete 资源组管理', 22, 'delete_resourcegroup'),
(140, 'Can view 资源组管理', 22, 'view_resourcegroup'),
(141, 'Can add SQL工单', 23, 'add_sqlworkflow'),
(142, 'Can change SQL工单', 23, 'change_sqlworkflow'),
(143, 'Can delete SQL工单', 23, 'delete_sqlworkflow'),
(144, 'Can view SQL工单', 23, 'view_sqlworkflow'),
(145, 'Can add 隧道配置', 24, 'add_tunnel'),
(146, 'Can change 隧道配置', 24, 'change_tunnel'),
(147, 'Can delete 隧道配置', 24, 'delete_tunnel'),
(148, 'Can view 隧道配置', 24, 'view_tunnel'),
(149, 'Can add 工作流审批明细', 25, 'add_workflowauditdetail'),
(150, 'Can change 工作流审批明细', 25, 'change_workflowauditdetail'),
(151, 'Can delete 工作流审批明细', 25, 'delete_workflowauditdetail'),
(152, 'Can view 工作流审批明细', 25, 'view_workflowauditdetail'),
(153, 'Can add 工作流日志', 26, 'add_workflowlog'),
(154, 'Can change 工作流日志', 26, 'change_workflowlog'),
(155, 'Can delete 工作流日志', 26, 'delete_workflowlog'),
(156, 'Can view 工作流日志', 26, 'view_workflowlog'),
(157, 'Can add 审批流程配置', 27, 'add_workflowauditsetting'),
(158, 'Can change 审批流程配置', 27, 'change_workflowauditsetting'),
(159, 'Can delete 审批流程配置', 27, 'delete_workflowauditsetting'),
(160, 'Can view 审批流程配置', 27, 'view_workflowauditsetting'),
(161, 'Can add 工作流审批列表', 28, 'add_workflowaudit'),
(162, 'Can change 工作流审批列表', 28, 'change_workflowaudit'),
(163, 'Can delete 工作流审批列表', 28, 'delete_workflowaudit'),
(164, 'Can view 工作流审批列表', 28, 'view_workflowaudit'),
(165, 'Can add SQL工单内容', 29, 'add_sqlworkflowcontent'),
(166, 'Can change SQL工单内容', 29, 'change_sqlworkflowcontent'),
(167, 'Can delete SQL工单内容', 29, 'delete_sqlworkflowcontent'),
(168, 'Can view SQL工单内容', 29, 'view_sqlworkflowcontent'),
(169, 'Can add 查询权限申请记录表', 30, 'add_queryprivilegesapply'),
(170, 'Can change 查询权限申请记录表', 30, 'change_queryprivilegesapply'),
(171, 'Can delete 查询权限申请记录表', 30, 'delete_queryprivilegesapply'),
(172, 'Can view 查询权限申请记录表', 30, 'view_queryprivilegesapply'),
(173, 'Can add 实例参数模板配置', 31, 'add_paramtemplate'),
(174, 'Can change 实例参数模板配置', 31, 'change_paramtemplate'),
(175, 'Can delete 实例参数模板配置', 31, 'delete_paramtemplate'),
(176, 'Can view 实例参数模板配置', 31, 'view_paramtemplate'),
(177, 'Can add 实例参数修改历史', 32, 'add_paramhistory'),
(178, 'Can change 实例参数修改历史', 32, 'change_paramhistory'),
(179, 'Can delete 实例参数修改历史', 32, 'delete_paramhistory'),
(180, 'Can view 实例参数修改历史', 32, 'view_paramhistory'),
(181, 'Can add 脱敏字段配置', 33, 'add_datamaskingcolumns'),
(182, 'Can change 脱敏字段配置', 33, 'change_datamaskingcolumns'),
(183, 'Can delete 脱敏字段配置', 33, 'delete_datamaskingcolumns'),
(184, 'Can view 脱敏字段配置', 33, 'view_datamaskingcolumns'),
(185, 'Can add 归档日志表', 34, 'add_archivelog'),
(186, 'Can change 归档日志表', 34, 'change_archivelog'),
(187, 'Can delete 归档日志表', 34, 'delete_archivelog'),
(188, 'Can view 归档日志表', 34, 'view_archivelog'),
(189, 'Can add 阿里云rds配置', 35, 'add_aliyunrdsconfig'),
(190, 'Can change 阿里云rds配置', 35, 'change_aliyunrdsconfig'),
(191, 'Can delete 阿里云rds配置', 35, 'delete_aliyunrdsconfig'),
(192, 'Can view 阿里云rds配置', 35, 'view_aliyunrdsconfig'),
(193, 'Can add 用户管理', 36, 'add_users'),
(194, 'Can change 用户管理', 36, 'change_users'),
(195, 'Can delete 用户管理', 36, 'delete_users'),
(196, 'Can view 用户管理', 36, 'view_users'),
(197, 'Can add 2FA配置', 37, 'add_twofactorauthconfig'),
(198, 'Can change 2FA配置', 37, 'change_twofactorauthconfig'),
(199, 'Can delete 2FA配置', 37, 'delete_twofactorauthconfig'),
(200, 'Can view 2FA配置', 37, 'view_twofactorauthconfig'),
(201, 'Can add 查询权限记录', 38, 'add_queryprivileges'),
(202, 'Can change 查询权限记录', 38, 'change_queryprivileges'),
(203, 'Can delete 查询权限记录', 38, 'delete_queryprivileges'),
(204, 'Can view 查询权限记录', 38, 'view_queryprivileges'),
(205, 'Can add 实例数据库', 39, 'add_instancedatabase'),
(206, 'Can change 实例数据库', 39, 'change_instancedatabase'),
(207, 'Can delete 实例数据库', 39, 'delete_instancedatabase'),
(208, 'Can view 实例数据库', 39, 'view_instancedatabase'),
(209, 'Can add 实例账号列表', 40, 'add_instanceaccount'),
(210, 'Can change 实例账号列表', 40, 'change_instanceaccount'),
(211, 'Can delete 实例账号列表', 40, 'delete_instanceaccount'),
(212, 'Can view 实例账号列表', 40, 'view_instanceaccount');
-- 导出 表 htmltooarchery.cloud_access_key 结构
DROP TABLE IF EXISTS `cloud_access_key`;
CREATE TABLE IF NOT EXISTS `cloud_access_key` (
`id` int NOT NULL AUTO_INCREMENT,
`type` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`key_id` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`key_secret` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`remark` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.cloud_access_key 的数据：~0 rows (大约)
DELETE FROM `cloud_access_key`;
-- 导出 表 htmltooarchery.data_masking_columns 结构
DROP TABLE IF EXISTS `data_masking_columns`;
CREATE TABLE IF NOT EXISTS `data_masking_columns` (
`column_id` int NOT NULL AUTO_INCREMENT,
`rule_type` int NOT NULL,
`active` tinyint(1) NOT NULL,
`table_schema` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`table_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`column_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`column_comment` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`column_id`),
KEY `data_masking_columns_instance_id_470661d3_fk_sql_instance_id` (`instance_id`),
CONSTRAINT `data_masking_columns_instance_id_470661d3_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.data_masking_columns 的数据：~0 rows (大约)
DELETE FROM `data_masking_columns`;
-- 导出 表 htmltooarchery.data_masking_rules 结构
DROP TABLE IF EXISTS `data_masking_rules`;
CREATE TABLE IF NOT EXISTS `data_masking_rules` (
`id` int NOT NULL AUTO_INCREMENT,
`rule_type` int NOT NULL,
`rule_regex` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`hide_group` int NOT NULL,
`rule_desc` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `rule_type` (`rule_type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.data_masking_rules 的数据：~0 rows (大约)
DELETE FROM `data_masking_rules`;
-- 导出 表 htmltooarchery.django_admin_log 结构
DROP TABLE IF EXISTS `django_admin_log`;
CREATE TABLE IF NOT EXISTS `django_admin_log` (
`id` int NOT NULL AUTO_INCREMENT,
`action_time` datetime(6) NOT NULL,
`object_id` longtext COLLATE utf8mb4_general_ci,
`object_repr` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`action_flag` smallint unsigned NOT NULL,
`change_message` longtext COLLATE utf8mb4_general_ci NOT NULL,
`content_type_id` int DEFAULT NULL,
`user_id` int NOT NULL,
PRIMARY KEY (`id`),
KEY `django_admin_log_content_type_id_c4bce8eb_fk_django_co` (`content_type_id`),
KEY `django_admin_log_user_id_c564eba6_fk_sql_users_id` (`user_id`),
CONSTRAINT `django_admin_log_content_type_id_c4bce8eb_fk_django_co` FOREIGN KEY (`content_type_id`) REFERENCES `django_content_type` (`id`),
CONSTRAINT `django_admin_log_user_id_c564eba6_fk_sql_users_id` FOREIGN KEY (`user_id`) REFERENCES `sql_users` (`id`),
CONSTRAINT `django_admin_log_chk_1` CHECK ((`action_flag` >= 0))
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_admin_log 的数据：~0 rows (大约)
DELETE FROM `django_admin_log`;
INSERT INTO `django_admin_log` (`id`, `action_time`, `object_id`, `object_repr`, `action_flag`, `change_message`, `content_type_id`, `user_id`) VALUES
(1, '2023-11-14 15:53:13.882890', '1', 'mariadb', 1, '[{"added": {}}]', 18, 1),
(2, '2023-11-14 15:54:37.842349', '1', '测试组', 1, '[{"added": {}}]', 22, 1);
-- 导出 表 htmltooarchery.django_content_type 结构
DROP TABLE IF EXISTS `django_content_type`;
CREATE TABLE IF NOT EXISTS `django_content_type` (
`id` int NOT NULL AUTO_INCREMENT,
`app_label` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`model` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `django_content_type_app_label_model_76bd3d3b_uniq` (`app_label`,`model`)
) ENGINE=InnoDB AUTO_INCREMENT=41 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_content_type 的数据：~0 rows (大约)
DELETE FROM `django_content_type`;
INSERT INTO `django_content_type` (`id`, `app_label`, `model`) VALUES
(1, 'admin', 'logentry'),
(3, 'auth', 'group'),
(2, 'auth', 'permission'),
(4, 'contenttypes', 'contenttype'),
(8, 'django_q', 'failure'),
(10, 'django_q', 'ormq'),
(6, 'django_q', 'schedule'),
(9, 'django_q', 'success'),
(7, 'django_q', 'task'),
(5, 'sessions', 'session'),
(35, 'sql', 'aliyunrdsconfig'),
(13, 'sql', 'archiveconfig'),
(34, 'sql', 'archivelog'),
(14, 'sql', 'auditentry'),
(15, 'sql', 'cloudaccesskey'),
(16, 'sql', 'config'),
(33, 'sql', 'datamaskingcolumns'),
(17, 'sql', 'datamaskingrules'),
(18, 'sql', 'instance'),
(40, 'sql', 'instanceaccount'),
(39, 'sql', 'instancedatabase'),
(19, 'sql', 'instancetag'),
(32, 'sql', 'paramhistory'),
(31, 'sql', 'paramtemplate'),
(20, 'sql', 'permission'),
(21, 'sql', 'querylog'),
(38, 'sql', 'queryprivileges'),
(30, 'sql', 'queryprivilegesapply'),
(22, 'sql', 'resourcegroup'),
(11, 'sql', 'slowquery'),
(12, 'sql', 'slowqueryhistory'),
(23, 'sql', 'sqlworkflow'),
(29, 'sql', 'sqlworkflowcontent'),
(24, 'sql', 'tunnel'),
(37, 'sql', 'twofactorauthconfig'),
(36, 'sql', 'users'),
(28, 'sql', 'workflowaudit'),
(25, 'sql', 'workflowauditdetail'),
(27, 'sql', 'workflowauditsetting'),
(26, 'sql', 'workflowlog');
-- 导出 表 htmltooarchery.django_migrations 结构
DROP TABLE IF EXISTS `django_migrations`;
CREATE TABLE IF NOT EXISTS `django_migrations` (
`id` int NOT NULL AUTO_INCREMENT,
`app` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`name` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`applied` datetime(6) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=34 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_migrations 的数据：~14 rows (大约)
DELETE FROM `django_migrations`;
INSERT INTO `django_migrations` (`id`, `app`, `name`, `applied`) VALUES
(1, 'contenttypes', '0001_initial', '2023-11-14 13:07:25.336465'),
(2, 'contenttypes', '0002_remove_content_type_name', '2023-11-14 13:07:25.519396'),
(3, 'auth', '0001_initial', '2023-11-14 13:07:26.614300'),
(4, 'auth', '0002_alter_permission_name_max_length', '2023-11-14 13:07:26.765258'),
(5, 'auth', '0003_alter_user_email_max_length', '2023-11-14 13:07:26.785362'),
(6, 'auth', '0004_alter_user_username_opts', '2023-11-14 13:07:26.801562'),
(7, 'auth', '0005_alter_user_last_login_null', '2023-11-14 13:07:26.827250'),
(8, 'auth', '0006_require_contenttypes_0002', '2023-11-14 13:07:26.832521'),
(9, 'auth', '0007_alter_validators_add_error_messages', '2023-11-14 13:07:26.859941'),
(10, 'auth', '0008_alter_user_username_max_length', '2023-11-14 13:07:26.893570'),
(11, 'auth', '0009_alter_user_last_name_max_length', '2023-11-14 13:07:26.910275'),
(12, 'auth', '0010_alter_group_name_max_length', '2023-11-14 13:07:26.970326'),
(13, 'auth', '0011_update_proxy_permissions', '2023-11-14 13:07:26.989290'),
(14, 'auth', '0012_alter_user_first_name_max_length', '2023-11-14 13:07:27.004263'),
(15, 'sql', '0001_initial', '2023-11-14 13:07:41.266254'),
(16, 'admin', '0001_initial', '2023-11-14 13:07:41.955630'),
(17, 'admin', '0002_logentry_remove_auto_add', '2023-11-14 13:07:42.004839'),
(18, 'admin', '0003_logentry_add_action_flag_choices', '2023-11-14 13:07:42.037192'),
(19, 'django_q', '0001_initial', '2023-11-14 13:07:42.134890'),
(20, 'django_q', '0002_auto_20150630_1624', '2023-11-14 13:07:42.252223'),
(21, 'django_q', '0003_auto_20150708_1326', '2023-11-14 13:07:42.430639'),
(22, 'django_q', '0004_auto_20150710_1043', '2023-11-14 13:07:42.476280'),
(23, 'django_q', '0005_auto_20150718_1506', '2023-11-14 13:07:42.643238'),
(24, 'django_q', '0006_auto_20150805_1817', '2023-11-14 13:07:42.959968'),
(25, 'django_q', '0007_ormq', '2023-11-14 13:07:43.182905'),
(26, 'django_q', '0008_auto_20160224_1026', '2023-11-14 13:07:43.271596'),
(27, 'django_q', '0009_auto_20171009_0915', '2023-11-14 13:07:43.833107'),
(28, 'django_q', '0010_auto_20200610_0856', '2023-11-14 13:07:43.868084'),
(29, 'django_q', '0011_auto_20200628_1055', '2023-11-14 13:07:43.954693'),
(30, 'django_q', '0012_auto_20200702_1608', '2023-11-14 13:07:43.986772'),
(31, 'django_q', '0013_task_attempt_count', '2023-11-14 13:07:44.163145'),
(32, 'django_q', '0014_schedule_cluster', '2023-11-14 13:07:44.267494'),
(33, 'sessions', '0001_initial', '2023-11-14 13:07:44.443009');
-- 导出 表 htmltooarchery.django_q_ormq 结构
DROP TABLE IF EXISTS `django_q_ormq`;
CREATE TABLE IF NOT EXISTS `django_q_ormq` (
`id` int NOT NULL AUTO_INCREMENT,
`key` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`payload` longtext COLLATE utf8mb4_general_ci NOT NULL,
`lock` datetime(6) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_q_ormq 的数据：~0 rows (大约)
DELETE FROM `django_q_ormq`;
-- 导出 表 htmltooarchery.django_q_schedule 结构
DROP TABLE IF EXISTS `django_q_schedule`;
CREATE TABLE IF NOT EXISTS `django_q_schedule` (
`id` int NOT NULL AUTO_INCREMENT,
`func` varchar(256) COLLATE utf8mb4_general_ci NOT NULL,
`hook` varchar(256) COLLATE utf8mb4_general_ci DEFAULT NULL,
`args` longtext COLLATE utf8mb4_general_ci,
`kwargs` longtext COLLATE utf8mb4_general_ci,
`schedule_type` varchar(1) COLLATE utf8mb4_general_ci NOT NULL,
`repeats` int NOT NULL,
`next_run` datetime(6) DEFAULT NULL,
`task` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
`name` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
`minutes` smallint unsigned DEFAULT NULL,
`cron` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
`cluster` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
PRIMARY KEY (`id`),
CONSTRAINT `django_q_schedule_chk_1` CHECK ((`minutes` >= 0))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_q_schedule 的数据：~0 rows (大约)
DELETE FROM `django_q_schedule`;
-- 导出 表 htmltooarchery.django_q_task 结构
DROP TABLE IF EXISTS `django_q_task`;
CREATE TABLE IF NOT EXISTS `django_q_task` (
`name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`func` varchar(256) COLLATE utf8mb4_general_ci NOT NULL,
`hook` varchar(256) COLLATE utf8mb4_general_ci DEFAULT NULL,
`args` longtext COLLATE utf8mb4_general_ci,
`kwargs` longtext COLLATE utf8mb4_general_ci,
`result` longtext COLLATE utf8mb4_general_ci,
`started` datetime(6) NOT NULL,
`stopped` datetime(6) NOT NULL,
`success` tinyint(1) NOT NULL,
`id` varchar(32) COLLATE utf8mb4_general_ci NOT NULL,
`group` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
`attempt_count` int NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_q_task 的数据：~0 rows (大约)
DELETE FROM `django_q_task`;
-- 导出 表 htmltooarchery.django_session 结构
DROP TABLE IF EXISTS `django_session`;
CREATE TABLE IF NOT EXISTS `django_session` (
`session_key` varchar(40) COLLATE utf8mb4_general_ci NOT NULL,
`session_data` longtext COLLATE utf8mb4_general_ci NOT NULL,
`expire_date` datetime(6) NOT NULL,
PRIMARY KEY (`session_key`),
KEY `django_session_expire_date_a5c62663` (`expire_date`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.django_session 的数据：~1 rows (大约)
DELETE FROM `django_session`;
INSERT INTO `django_session` (`session_key`, `session_data`, `expire_date`) VALUES
('xz7yy60ynoqw96hvd8fo7spj0ot1c5nl', '.eJxVjckOwyAMRP-Fc4UwkPXYe78BsTiFLlBBUjWq-u8lUi65WPa8mfGXLAUzGUnwS5zrdiJvzGFa1TM5rPp-pfhYK1MFSwkpKvy8Ql7JCD1jrOp6mb3aqlRwNQXkoBlt7xg34G46XhO1Kc45GLpZ6E4LvdSXj_PuPRR4XXxNG2c6aHFyrZSgOccBjG247CxYZoUz3EyWYyedqBPE0OpGi6E3sgHOwZHfH1SiT9U:1r2oSp:4Td--RYpVFhY-mhzX_ObLEGFa-nfajG751BEVeo5zTg', '2023-11-14 21:08:03.761611');
-- 导出 表 htmltooarchery.instance_account 结构
DROP TABLE IF EXISTS `instance_account`;
CREATE TABLE IF NOT EXISTS `instance_account` (
`id` int NOT NULL AUTO_INCREMENT,
`user` varchar(128) COLLATE utf8mb4_general_ci NOT NULL,
`host` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`db_name` varchar(128) COLLATE utf8mb4_general_ci NOT NULL DEFAULT '' COMMENT '数据库名（mongodb）',
`password` varchar(128) COLLATE utf8mb4_general_ci NOT NULL,
`remark` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`sys_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `instance_account_instance_id_user_host_514c1ac6_uniq` (`instance_id`,`user`,`host`),
UNIQUE KEY `uidx_instanceid_user_host_dbname` (`instance_id`,`user`,`host`,`db_name`),
CONSTRAINT `instance_account_instance_id_53a7a305_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.instance_account 的数据：~0 rows (大约)
DELETE FROM `instance_account`;
-- 导出 表 htmltooarchery.instance_database 结构
DROP TABLE IF EXISTS `instance_database`;
CREATE TABLE IF NOT EXISTS `instance_database` (
`id` int NOT NULL AUTO_INCREMENT,
`db_name` varchar(128) COLLATE utf8mb4_general_ci NOT NULL,
`owner` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`owner_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`remark` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`sys_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `instance_database_instance_id_db_name_d8700935_uniq` (`instance_id`,`db_name`),
CONSTRAINT `instance_database_instance_id_22c69243_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.instance_database 的数据：~0 rows (大约)
DELETE FROM `instance_database`;
-- 导出 表 htmltooarchery.mysql_slow_query_review 结构
DROP TABLE IF EXISTS `mysql_slow_query_review`;
CREATE TABLE IF NOT EXISTS `mysql_slow_query_review` (
`checksum` char(32) NOT NULL,
`fingerprint` longtext NOT NULL,
`sample` longtext NOT NULL,
`first_seen` datetime(6) DEFAULT NULL,
`last_seen` datetime(6) DEFAULT NULL,
`reviewed_by` varchar(20) DEFAULT NULL,
`reviewed_on` datetime(6) DEFAULT NULL,
`comments` longtext,
`reviewed_status` varchar(24) DEFAULT NULL,
PRIMARY KEY (`checksum`),
KEY `idx_last_seen` (`last_seen`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
-- 正在导出表 htmltooarchery.mysql_slow_query_review 的数据：~0 rows (大约)
DELETE FROM `mysql_slow_query_review`;
-- 导出 表 htmltooarchery.mysql_slow_query_review_history 结构
DROP TABLE IF EXISTS `mysql_slow_query_review_history`;
CREATE TABLE IF NOT EXISTS `mysql_slow_query_review_history` (
`id` int NOT NULL AUTO_INCREMENT,
`hostname_max` varchar(64) NOT NULL,
`client_max` varchar(64) DEFAULT NULL,
`user_max` varchar(64) NOT NULL,
`db_max` varchar(64) DEFAULT NULL,
`checksum` char(32) NOT NULL,
`sample` longtext NOT NULL,
`ts_min` datetime(6) NOT NULL,
`ts_max` datetime(6) NOT NULL,
`ts_cnt` float DEFAULT NULL,
`Query_time_sum` float DEFAULT NULL,
`Query_time_min` float DEFAULT NULL,
`Query_time_max` float DEFAULT NULL,
`Query_time_pct_95` float DEFAULT NULL,
`Query_time_stddev` float DEFAULT NULL,
`Query_time_median` float DEFAULT NULL,
`Lock_time_sum` float DEFAULT NULL,
`Lock_time_min` float DEFAULT NULL,
`Lock_time_max` float DEFAULT NULL,
`Lock_time_pct_95` float DEFAULT NULL,
`Lock_time_stddev` float DEFAULT NULL,
`Lock_time_median` float DEFAULT NULL,
`Rows_sent_sum` float DEFAULT NULL,
`Rows_sent_min` float DEFAULT NULL,
`Rows_sent_max` float DEFAULT NULL,
`Rows_sent_pct_95` float DEFAULT NULL,
`Rows_sent_stddev` float DEFAULT NULL,
`Rows_sent_median` float DEFAULT NULL,
`Rows_examined_sum` float DEFAULT NULL,
`Rows_examined_min` float DEFAULT NULL,
`Rows_examined_max` float DEFAULT NULL,
`Rows_examined_pct_95` float DEFAULT NULL,
`Rows_examined_stddev` float DEFAULT NULL,
`Rows_examined_median` float DEFAULT NULL,
`Rows_affected_sum` float DEFAULT NULL,
`Rows_affected_min` float DEFAULT NULL,
`Rows_affected_max` float DEFAULT NULL,
`Rows_affected_pct_95` float DEFAULT NULL,
`Rows_affected_stddev` float DEFAULT NULL,
`Rows_affected_median` float DEFAULT NULL,
`Rows_read_sum` float DEFAULT NULL,
`Rows_read_min` float DEFAULT NULL,
`Rows_read_max` float DEFAULT NULL,
`Rows_read_pct_95` float DEFAULT NULL,
`Rows_read_stddev` float DEFAULT NULL,
`Rows_read_median` float DEFAULT NULL,
`Merge_passes_sum` float DEFAULT NULL,
`Merge_passes_min` float DEFAULT NULL,
`Merge_passes_max` float DEFAULT NULL,
`Merge_passes_pct_95` float DEFAULT NULL,
`Merge_passes_stddev` float DEFAULT NULL,
`Merge_passes_median` float DEFAULT NULL,
`InnoDB_IO_r_ops_min` float DEFAULT NULL,
`InnoDB_IO_r_ops_max` float DEFAULT NULL,
`InnoDB_IO_r_ops_pct_95` float DEFAULT NULL,
`InnoDB_IO_r_ops_stddev` float DEFAULT NULL,
`InnoDB_IO_r_ops_median` float DEFAULT NULL,
`InnoDB_IO_r_bytes_min` float DEFAULT NULL,
`InnoDB_IO_r_bytes_max` float DEFAULT NULL,
`InnoDB_IO_r_bytes_pct_95` float DEFAULT NULL,
`InnoDB_IO_r_bytes_stddev` float DEFAULT NULL,
`InnoDB_IO_r_bytes_median` float DEFAULT NULL,
`InnoDB_IO_r_wait_min` float DEFAULT NULL,
`InnoDB_IO_r_wait_max` float DEFAULT NULL,
`InnoDB_IO_r_wait_pct_95` float DEFAULT NULL,
`InnoDB_IO_r_wait_stddev` float DEFAULT NULL,
`InnoDB_IO_r_wait_median` float DEFAULT NULL,
`InnoDB_rec_lock_wait_min` float DEFAULT NULL,
`InnoDB_rec_lock_wait_max` float DEFAULT NULL,
`InnoDB_rec_lock_wait_pct_95` float DEFAULT NULL,
`InnoDB_rec_lock_wait_stddev` float DEFAULT NULL,
`InnoDB_rec_lock_wait_median` float DEFAULT NULL,
`InnoDB_queue_wait_min` float DEFAULT NULL,
`InnoDB_queue_wait_max` float DEFAULT NULL,
`InnoDB_queue_wait_pct_95` float DEFAULT NULL,
`InnoDB_queue_wait_stddev` float DEFAULT NULL,
`InnoDB_queue_wait_median` float DEFAULT NULL,
`InnoDB_pages_distinct_min` float DEFAULT NULL,
`InnoDB_pages_distinct_max` float DEFAULT NULL,
`InnoDB_pages_distinct_pct_95` float DEFAULT NULL,
`InnoDB_pages_distinct_stddev` float DEFAULT NULL,
`InnoDB_pages_distinct_median` float DEFAULT NULL,
`QC_Hit_cnt` float DEFAULT NULL,
`QC_Hit_sum` float DEFAULT NULL,
`Full_scan_cnt` float DEFAULT NULL,
`Full_scan_sum` float DEFAULT NULL,
`Full_join_cnt` float DEFAULT NULL,
`Full_join_sum` float DEFAULT NULL,
`Tmp_table_cnt` float DEFAULT NULL,
`Tmp_table_sum` float DEFAULT NULL,
`Tmp_table_on_disk_cnt` float DEFAULT NULL,
`Tmp_table_on_disk_sum` float DEFAULT NULL,
`Filesort_cnt` float DEFAULT NULL,
`Filesort_sum` float DEFAULT NULL,
`Filesort_on_disk_cnt` float DEFAULT NULL,
`Filesort_on_disk_sum` float DEFAULT NULL,
`Bytes_sum` float DEFAULT NULL,
`Bytes_min` float DEFAULT NULL,
`Bytes_max` float DEFAULT NULL,
`Bytes_pct_95` float DEFAULT NULL,
`Bytes_stddev` float DEFAULT NULL,
`Bytes_median` float DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `checksum` (`checksum`,`ts_min`,`ts_max`),
KEY `idx_hostname_max_ts_min` (`hostname_max`,`ts_min`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
-- 正在导出表 htmltooarchery.mysql_slow_query_review_history 的数据：~0 rows (大约)
DELETE FROM `mysql_slow_query_review_history`;
-- 导出 表 htmltooarchery.param_history 结构
DROP TABLE IF EXISTS `param_history`;
CREATE TABLE IF NOT EXISTS `param_history` (
`id` int NOT NULL AUTO_INCREMENT,
`variable_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`old_var` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`new_var` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`set_sql` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`user_name` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`id`),
KEY `param_history_instance_id_601e8d3f_fk_sql_instance_id` (`instance_id`),
CONSTRAINT `param_history_instance_id_601e8d3f_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.param_history 的数据：~0 rows (大约)
DELETE FROM `param_history`;
-- 导出 表 htmltooarchery.param_template 结构
DROP TABLE IF EXISTS `param_template`;
CREATE TABLE IF NOT EXISTS `param_template` (
`id` int NOT NULL AUTO_INCREMENT,
`db_type` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`variable_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`default_value` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`editable` tinyint(1) NOT NULL,
`valid_values` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`description` varchar(1024) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `param_template_db_type_variable_name_139c76a6_uniq` (`db_type`,`variable_name`)
) ENGINE=InnoDB AUTO_INCREMENT=417 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.param_template 的数据：~225 rows (大约)
DELETE FROM `param_template`;
INSERT INTO `param_template` (`id`, `db_type`, `variable_name`, `default_value`, `editable`, `valid_values`, `description`, `create_time`, `sys_time`) VALUES
(1, 'goinception', 'check_autoincrement_datatype', 'false', 1, 'true,false', '当建表时自增列的类型不为int或者bigint时报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(2, 'goinception', 'check_autoincrement_init_value', 'false', 1, 'true,false', '当建表时自增列的值指定的不为1，则报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(3, 'goinception', 'check_autoincrement_name', 'false', 1, 'true,false', '建表时，如果指定的自增列的名字不为ID，则报错，说明是有意义的，给提示', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(4, 'goinception', 'check_column_comment', 'false', 1, 'true,false', '建表时，列没有注释时报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(5, 'goinception', 'check_column_default_value', 'false', 1, 'true,false', '检查在建表、修改列、新增列时，新的列属性是不是要有默认值', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(6, 'goinception', 'check_column_type_change', 'true', 1, 'true,false', '检查字段类型变更', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(7, 'goinception', 'check_dml_limit', 'false', 1, 'true,false', '在DML语句中使用了LIMIT时，是不是要报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(8, 'goinception', 'check_dml_orderby', 'false', 1, 'true,false', '在DML语句中使用了Order By时，是不是要报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(9, 'goinception', 'check_dml_where', 'false', 1, 'true,false', '在DML语句中没有WHERE条件时，是不是要报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(10, 'goinception', 'check_identifier', 'false', 1, 'true,false', '检查标识符是否正确,规则是[a-z,A-Z,0-9,_]', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(11, 'goinception', 'check_index_prefix', 'false', 1, 'true,false', '是不是要检查索引名字前缀为"idx_"，检查唯一索引前缀是不是"uniq_"', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(12, 'goinception', 'check_insert_field', 'false', 1, 'true,false', '是不是要检查插入语句中的列链表的存在性', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(13, 'goinception', 'check_primary_key', 'false', 1, 'true,false', '建表时，如果没有主键，则报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(14, 'goinception', 'check_table_comment', 'false', 1, 'true,false', '建表时，表没有注释时报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(15, 'goinception', 'check_timestamp_count', 'false', 1, 'true,false', '配置是否检查current_timestamp数量', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(16, 'goinception', 'check_timestamp_default', 'false', 1, 'true,false', '建表时，如果没有为timestamp类型指定默认值，则报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(17, 'goinception', 'enable_autoincrement_unsigned', 'false', 1, 'true,false', '自增列是不是要为无符号型', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(18, 'goinception', 'enable_blob_type', 'false', 1, 'true,false', '检查是不是支持BLOB字段，包括建表、修改列、新增列操作', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(19, 'goinception', 'enable_column_charset', 'false', 1, 'true,false', '允许列自己设置字符集', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(20, 'goinception', 'enable_drop_database', 'false', 1, 'true,false', '是否允许删除数据库', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(21, 'goinception', 'enable_drop_table', 'false', 1, 'true,false', '是否允许删除表', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(22, 'goinception', 'enable_enum_set_bit', 'false', 1, 'true,false', '是不是支持enum,set,bit数据类型', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(23, 'goinception', 'enable_fingerprint', 'false', 1, 'true,false', 'sql指纹功能。dml语句较多相似时，可大幅优化审核速度', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(24, 'goinception', 'enable_foreign_key', 'false', 1, 'true,false', '是不是支持外键', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(25, 'goinception', 'enable_identifer_keyword', 'false', 1, 'true,false', '检查在SQL语句中，是不是有标识符被写成MySQL的关键字，默认值为报警。', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(26, 'goinception', 'enable_json_type', 'false', 1, 'true,false', '设置是否允许json类型字段，包括建表、修改列、新增列操作', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(27, 'goinception', 'enable_not_innodb', 'false', 1, 'true,false', '建表指定的存储引擎不为Innodb，不报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(28, 'goinception', 'enable_nullable', 'false', 1, 'true,false', '创建或者新增列时如果列为NULL，是不是报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(29, 'goinception', 'enable_null_index_name', 'false', 1, 'true,false', '创建索引时是否允许空索引名', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(30, 'goinception', 'enable_orderby_rand', 'false', 1, 'true,false', 'order by rand时是不是报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(31, 'goinception', 'enable_partition_table', 'false', 1, 'true,false', '是不是支持分区表', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(32, 'goinception', 'enable_pk_columns_only_int', 'false', 1, 'true,false', '是否强制主键列必须是int', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(33, 'goinception', 'enable_select_star', 'false', 1, 'true,false', 'Select*时是不是要报错', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(34, 'goinception', 'enable_set_charset', 'false', 1, 'true,false', '是否允许指定表和数据库的字符集', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(35, 'goinception', 'enable_set_collation', 'false', 1, 'true,false', '是否允许指定表和数据库的排序规则', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(36, 'goinception', 'general_log', 'false', 1, 'true,false', '是否记录全量日志', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(37, 'goinception', 'lang', 'en,-US', 1, 'en-US,zh-CN', '返回的信息使用语言,可选值`en-US`,`zh-CN`', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(38, 'goinception', 'max_char_length', '0', 1, 'int', '最大char长度,当超出时警告转换为varchar类型', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(39, 'goinception', 'max_insert_rows', '0', 1, 'int', '设置insert values允许的最大行数.0为不限制', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(40, 'goinception', 'max_key_parts', '3', 1, 'int', '一个索引最多可指定的列数', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(41, 'goinception', 'max_keys', '3', 1, 'int', '单表允许的最大索引数', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(42, 'goinception', 'max_primary_key_parts', '3', 1, 'int', '主键最多可指定的列数', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(43, 'goinception', 'max_update_rows', '5000', 1, 'int', '当update/delete预估受影响行数超出设置值时警告', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(44, 'goinception', 'merge_alter_table', 'false', 1, 'true,false', '在多个改同一个表的语句出现是，报错，提示合成一个', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(45, 'goinception', 'must_have_columns', '""', 1, 'string', '用以指定建表时必须创建的列。多个列时以逗号分隔(`格式: 列名 [列类型,可选]`)', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(46, 'goinception', 'sql_safe_updates', '-1', 1, '-1,0,1', '安全更新.-1表示不做操作,基于远端数据库,0表示关闭安全更新,1表示开启安全更新', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(47, 'goinception', 'support_charset', 'utf8,utf8mb4', 1, 'string', '支持的字符集,多个时以逗号分隔', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(48, 'goinception', 'support_collation', '""', 1, 'string', '支持的排序规则,多个时以逗号分隔', '2019-05-27 15:12:59.000000', '2019-05-27 15:12:59.000000'),
(49, 'goinception', 'osc_on', 'false', 1, 'bool', 'OSC开关', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(50, 'goinception', 'osc_alter_foreign_keys_method', 'none', 1, 'string', '对应OSC参数alter-foreign-keys-method', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(51, 'goinception', 'osc_bin_dir', '/usr/local/bin', 1, 'string', 'pt-online-schema-change脚本的位置', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(52, 'goinception', 'osc_check_alter', 'true', 1, 'bool', '对应参数--[no]check-alter', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(53, 'goinception', 'osc_check_interval', '5', 1, 'int', '对应参数--check-interval，意义是Sleep time between checks for --max-lag.', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(54, 'goinception', 'osc_check_replication_filters', 'true', 1, 'bool', '对应参数--[no]check-replication-filters', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(55, 'goinception', 'osc_chunk_size', '1000', 1, 'int', '对应参数--chunk-size', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(56, 'goinception', 'osc_chunk_size_limit', '4', 1, 'int', '对应参数--chunk-size-limit', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(57, 'goinception', 'osc_chunk_time', '1', 1, 'int', '对应参数--chunk-time', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(58, 'goinception', 'osc_critical_thread_connected', '1000', 1, 'int', '对应参数--critical-load中的thread_connected部分', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(59, 'goinception', 'osc_critical_thread_running', '80', 1, 'int', '对应参数--critical-load中的thread_running部分', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(60, 'goinception', 'osc_drop_new_table', 'true', 1, 'bool', '对应参数--[no]drop-new-table', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(61, 'goinception', 'osc_drop_old_table', 'true', 1, 'bool', '对应参数--[no]drop-old-table', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(62, 'goinception', 'osc_max_lag', '3', 1, 'int', '对应参数--max-lag', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(63, 'goinception', 'osc_max_thread_connected', '1000', 1, 'int', '对应参数--max-load中的thread_connected部分', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(64, 'goinception', 'osc_max_thread_running', '80', 1, 'int', '对应参数--max-load中的thread_running部分', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(65, 'goinception', 'osc_min_table_size', '16', 1, 'int', 'OSC的开关，如果设置为0，则全部ALTER语句都走OSC，如果设置为非0，则当这个表占用空间大小大于这个值时才使用OSC方式。单位为M，这个表大小的计算方式是通过语句： select (DATA_LENGTH + INDEX_LENGTH)/1024/1024 from information_schema.tables where table_schema = "dbname" and table_name = "tablename"来实现的。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(66, 'goinception', 'osc_print_none', 'false', 1, 'bool', '用来设置在Inception返回结果集中，对于原来OSC在执行过程的标准输出信息是不是要打印到结果集对应的错误信息列中，如果设置为1，就不打印，如果设置为0，就打印。而如果出现错误了，则都会打印', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(67, 'goinception', 'osc_print_sql', 'false', 1, 'bool', '对应参数--print', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(68, 'goinception', 'osc_recursion_method', 'processlist', 1, 'string', '对应参数recursion_method', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(69, 'goinception', 'ghost_on', 'false', 1, 'bool', 'gh-ost开关', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(70, 'goinception', 'ghost_aliyun_rds', 'false', 1, 'bool', '阿里云rds数据库标志', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(71, 'goinception', 'ghost_allow_master_master', 'false', 1, 'bool', '允许gh-ost运行在双主复制架构中，一般与-assume-master-host参数一起使用', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(72, 'goinception', 'ghost_allow_nullable_unique_key', 'false', 1, 'bool', '允许gh-ost在数据迁移(migrate)依赖的唯一键可以为NULL，默认为不允许为NULL的唯一键。如果数据迁移(migrate)依赖的唯一键允许NULL值，则可能造成数据不正确，请谨慎使用。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(73, 'goinception', 'ghost_allow_on_master', 'true', 1, 'bool', '允许gh-ost直接运行在主库上。默认gh-ost连接的`主库`。`(暂未添加从库地址的配置)`', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(74, 'goinception', 'ghost_approve_renamed_columns', 'true', 1, 'bool', '如果支持修改列名,则需设置此参数为`true`,否则gh-ost不会执行。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(75, 'goinception', 'ghost_assume_master_host', '""', 1, 'string', '为gh-ost指定一个主库，格式为"ip:port"或者"hostname:port"。默认推荐gh-ost连接从库。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(76, 'goinception', 'ghost_assume_rbr', 'true', 1, 'bool', '确认gh-ost连接的数据库实例的binlog_format=ROW的情况下，可以指定-assume-rbr，这样可以禁止从库上运行stop slave,start slave,执行gh-ost用户也不需要SUPER权限。`为避免影响生产数据库，此参数建议置为true`', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(77, 'goinception', 'ghost_chunk_size', '1000', 1, 'int', '在每次迭代中处理的行数量(允许范围：100-100000)，默认值为1000。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(78, 'goinception', 'ghost_concurrent_rowcount', 'true', 1, 'bool', '该参数如果为True(默认值)，则进行row-copy之后，估算统计行数(使用explain select count(*)方式)，并调整ETA时间，否则，gh-ost首先预估统计行数，然后开始row-copy。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(79, 'goinception', 'ghost_critical_load_hibernate_seconds', '0', 1, 'int', '负载达到critical-load时，gh-ost在指定的时间内进入休眠状态。 它不会读/写任何来自任何服务器的任何内容。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(80, 'goinception', 'ghost_critical_load_interval_millis', '0', 1, 'int', '当值为0时，当达到-critical-load，gh-ost立即退出。当值不为0时，当达到-critical-load，gh-ost会在-critical-load-interval-millis秒数后，再次进行检查，再次检查依旧达到-critical-load，gh-ost将会退出。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(81, 'goinception', 'ghost_cut_over', 'atomic', 1, 'string', '选择cut-over类型:atomic/two-step，atomic(默认)类型的cut-over是github的算法，two-step采用的是facebook-OSC的算法。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(82, 'goinception', 'ghost_cut_over_exponential_backoff', 'false', 1, 'bool', 'Wait exponentially longer intervals between failed cut-over attempts. Wait intervals obey a maximum configurable with \'exponential-backoff-max-interval\').', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(83, 'goinception', 'ghost_cut_over_lock_timeout_seconds', '3', 1, 'int', 'gh-ost在cut-over阶段最大的锁等待时间，当锁超时时，gh-ost的cut-over将重试。(默认值：3)', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(84, 'goinception', 'ghost_default_retries', '60', 1, 'int', '各种操作在panick前重试次数。(默认为60)', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(85, 'goinception', 'ghost_discard_foreign_keys', 'false', 1, 'bool', '该参数针对一个有外键的表，在gh-ost创建ghost表时，并不会为ghost表创建外键。该参数很适合用于删除外键，除此之外，请谨慎使用。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(86, 'goinception', 'ghost_dml_batch_size', '10', 1, 'int', '在单个事务中应用DML事件的批量大小（范围1-100）（默认值为10）', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(87, 'goinception', 'ghost_exact_rowcount', 'false', 1, 'bool', '准确统计表行数(使用select count(*)的方式)，得到更准确的预估时间。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(88, 'goinception', 'ghost_exponential_backoff_max_interval', '64', 1, 'int', 'Maximum number of seconds to wait between attempts when performing various operations with exponential backoff. (default 64)', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(89, 'goinception', 'ghost_force_named_cut_over', 'false', 1, 'bool', 'When true, the ‘unpostpone|cut-over’ interactive command must name the migrated table。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(90, 'goinception', 'ghost_force_table_names', '""', 1, 'string', 'table name prefix to be used on the temporary tables', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(91, 'goinception', 'ghost_gcp', 'false', 1, 'bool', 'google云平台支持', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(92, 'goinception', 'ghost_heartbeat_interval_millis', '500', 1, 'int', 'gh-ost心跳频率值，默认为500。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(93, 'goinception', 'ghost_initially_drop_ghost_table', 'false', 1, 'bool', 'gh-ost操作之前，检查并删除已经存在的ghost表。该参数不建议使用，请手动处理原来存在的ghost表。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(94, 'goinception', 'ghost_initially_drop_old_table', 'false', 1, 'bool', 'gh-ost操作之前，检查并删除已经存在的旧表。该参数不建议使用，请手动处理原来存在的ghost表。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(95, 'goinception', 'ghost_initially_drop_socket_file', 'false', 1, 'bool', 'gh-ost强制删除已经存在的socket文件。该参数不建议使用，可能会删除一个正在运行的gh-ost程序，导致DDL失败。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(96, 'goinception', 'ghost_max_lag_millis', '1500', 1, 'int', '主从复制最大延迟时间，当主从复制延迟时间超过该值后，gh-ost将采取节流(throttle)措施，默认值：1500s。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(97, 'goinception', 'ghost_nice_ratio', '0', 1, 'float', '每次chunk时间段的休眠时间，范围[0.0...100.0]。e.g:0：每个chunk时间段不休眠，即一个chunk接着一个chunk执行；1：每row-copy 1毫秒，则另外休眠1毫秒；0.7：每row-copy 10毫秒，则另外休眠7毫秒。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(98, 'goinception', 'ghost_ok_to_drop_table', 'true', 1, 'bool', 'gh-ost操作结束后，删除旧表，默认状态是`删除旧表`。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(99, 'goinception', 'ghost_postpone_cut_over_flag_file', '""', 1, 'string', '当这个文件存在的时候，gh-ost的cut-over阶段将会被推迟，直到该文件被删除。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(100, 'goinception', 'ghost_replication_lag_query', '""', 1, 'string', '检查主从复制延迟的SQL语句，默认gh-ost通过show slave status获取Seconds_behind_master作为主从延迟时间依据。如果使用pt-heartbeat工具，检查主从复制延迟的SQL语句类似于:`SELECT ROUND(UNIX_TIMESTAMP() - MAX(UNIX_TIMESTAMP(ts))) AS delay FROM my_schema.heartbeat`;', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(101, 'goinception', 'ghost_skip_foreign_key_checks', 'true', 1, 'bool', '跳过外键检查,默认为`true`', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(102, 'goinception', 'ghost_throttle_additional_flag_file', '""', 1, 'string', '当该文件被创建后，gh-ost操作立即停止。该参数可以用在多个gh-ost同时操作的时候，创建一个文件，让所有的gh-ost操作停止，或者删除这个文件，让所有的gh-ost操作恢复。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(103, 'goinception', 'ghost_throttle_control_replicas', '""', 1, 'string', '列出所有需要被检查主从复制延迟的从库。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(104, 'goinception', 'ghost_throttle_flag_file', '""', 1, 'string', '当该文件被创建后，gh-ost操作立即停止。该参数适合控制单个gh-ost操作。-throttle-additional-flag-file string适合控制多个gh-ost操作。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(105, 'goinception', 'ghost_throttle_http', '""', 1, 'string', 'The --throttle-http flag allows for throttling via HTTP. Every 100ms gh-ost issues a HEAD request to the provided URL. If the response status code is not 200 throttling will kick in until a 200 response status code is returned.', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(106, 'goinception', 'ghost_throttle_query', '""', 1, 'string', '节流查询。每秒钟执行一次。当返回值=0时不需要节流，当返回值>0时，需要执行节流操作。该查询会在数据迁移(migrated)服务器上操作，所以请确保该查询是轻量级的。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(107, 'goinception', 'ghost_timestamp_old_table', 'false', 1, 'bool', '在旧表名中使用时间戳。 这会使旧表名称具有唯一且无冲突的交叉迁移', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(108, 'goinception', 'ghost_tungsten', 'false', 1, 'bool', '告诉gh-ost你正在运行的是一个tungsten-replication拓扑结构。', '2019-05-27 15:25:11.000000', '2019-05-27 15:25:11.000000'),
(217, 'mysql', 'automatic_sp_privileges', 'ON', 1, '[ON|OFF]', 'When this variable has a value of 1 (the default), the server automatically grants the EXECUTE and ALTER ROUTINE privileges to the creator of a stored routine, if the user cannot already execute and alter or drop the routine. (The ALTER ROUTINE privilege is required to drop the routine.) The server also automatically drops those privileges from the creator when the routine is dropped. If automatic_sp_privileges is 0, the server does not automatically add or drop these privileges.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(218, 'mysql', 'auto_increment_increment', '1', 1, '[1-65535]', 'Auto-increment columns are incremented by this', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(219, 'mysql', 'auto_increment_offset', '1', 1, '[1-65535]', 'Offset added to Auto-increment columns. Used when auto-increment-increment != 1', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(220, 'mysql', 'avoid_temporal_upgrade', 'OFF', 1, '[ON|OFF]', 'This variable controls whether ALTER TABLE implicitly upgrades temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). Upgrading such columns requires a table rebuild, which prevents any use of fast alterations that might otherwise apply to the operation to be performed.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(221, 'mysql', 'back_log', '3000', 0, '[0-65535]', 'The number of outstanding connection requests MySQL can have. This comes into play when the main MySQL thread gets very many connection requests in a very short time', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(222, 'mysql', 'binlog_cache_size', '2097152', 1, '[4096-16777216]', 'The size of the transactional cache for updates to transactional engines for the binary log. If you often use transactions containing many statements, you can increase this to get more performance', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(223, 'mysql', 'binlog_checksum', 'CRC32', 0, '[CRC32|NONE]', 'Type of BINLOG_CHECKSUM_ALG. Include checksum for log events in the binary log. Possible values are NONE and CRC32; default is CRC32.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(224, 'mysql', 'binlog_order_commits', 'ON', 1, '[ON|OFF]', 'When this variable is enabled on a master (the default), transactions are externalized in the same order as they are written to the binary log. If disabled, transactions may be committed in parallel. In some cases, disabling this variable might produce a performance increment.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(225, 'mysql', 'binlog_rows_query_log_events', 'OFF', 1, '[ON|OFF]', 'The binlog_rows_query_log_events system variable affects row-based logging only. When enabled, it causes the MySQL Server to write informational log events such as row query log events into its binary log. This information can be used for debugging and related purposes.such as obtaining the original query issued on the master when it cannot be reconstructed from the row updates.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(226, 'mysql', 'binlog_row_image', 'full', 1, '[full|minimal]', 'Controls whether rows should be logged in \'FULL\', \'NOBLOB\' or \'MINIMAL\' formats. \'FULL\', means that all columns in the before and after image are logged. \'NOBLOB\', means that mysqld avoids logging blob columns whenever possible (eg, blob column was not changed or is not part of primary key). \'MINIMAL\', means that a PK equivalent (PK columns or full row if there is no PK in the table) is logged in the before image, and only changed columns are logged in the after image. (Default: FULL).', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(227, 'mysql', 'binlog_stmt_cache_size', '32768', 1, '[4096-16777216]', 'The size of the statement cache for updates to non-transactional engines for the binary log. If you often use statements updating a great number of rows, you can increase this to get more performance', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(228, 'mysql', 'block_encryption_mode', '"aes-128-ecb"', 1, '["aes-128-ecb"|"aes-192-ecb"|"aes-256-ecb"|"aes-128-cbc"|"aes-192-cbc"|"aes-256-cbc"]', 'This variable controls the block encryption mode for block-based algorithms such as AES. It affects encryption for AES_ENCRYPT() and AES_DECRYPT().', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(229, 'mysql', 'bulk_insert_buffer_size', '4194304', 1, '[0-4294967295]', 'MyISAM uses a special tree-like cache to make bulk inserts faster for INSERT ... SELECT, INSERT ... VALUES (...), (...), ..., and LOAD DATA INFILE when adding data to nonempty tables. This variable limits the size of the cache tree in bytes per thread. Setting it to 0 disables this optimization. The default value is 8MB.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(230, 'mysql', 'character_set_filesystem', 'binary', 1, '[utf8|latin1|gbk|binary]', 'The file system character set. This variable is used to interpret string literals that refer to file names, such as in the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements and the LOAD_FILE() function. Such file names are converted from character_set_client to character_set_filesystem before the file opening attempt occurs. The default value is binary, which means that no conversion occurs. For systems on which multibyte file names are permitted, a different value may be more appropriate. For example, if the system represents file names using UTF-8, set character_set_filesystem to \'utf8\'.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(231, 'mysql', 'character_set_server', 'utf8', 0, '[utf8|latin1|gbk|utf8mb4]', 'The default character set', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(232, 'mysql', 'concurrent_insert', '1', 1, '[0|1|2]', 'Use concurrent insert with MyISAM. Possible values are NEVER, AUTO, ALWAYS', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(233, 'mysql', 'connect_timeout', '10', 1, '[1-3600]', 'The number of seconds the mysqld server is waiting for a connect packet before responding with \'Bad handshake\'', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(234, 'mysql', 'default_storage_engine', 'InnoDB', 0, '[InnoDB|innodb]', 'The default storage engine for new tables', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(235, 'mysql', 'default_time_zone', 'SYSTEM', 0, '[SYSTEM|-12:00|-11:00|-10:00|-9:00|-8:00|-7:00|-6:00|-5:00|-4:00|-3:00|-2:00|-1:00|\\+0:00|\\+1:00|\\+2:00|\\+3:00|\\+4:00|\\+5:00|\\+5:30|\\+6:00|\\+6:30|\\+7:00|\\+8:00|\\+9:00|\\+10:00|\\+11:00|\\+12:00|\\+13:00]', 'The default time zone for the database', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(236, 'mysql', 'default_week_format', '0', 1, '[0-7]', 'The default week format used by WEEK() functions', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(237, 'mysql', 'delayed_insert_limit', '100', 1, '[1-4294967295]', 'After inserting delayed_insert_limit rows, the INSERT DELAYED handler will check if there are any SELECT statements pending. If so, it allows these to execute before continuing. This variable is deprecated along with INSERT DELAYED.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(238, 'mysql', 'delayed_insert_timeout', '300', 1, '[1-3600]', 'How long a INSERT DELAYED thread should wait for INSERT statements before terminating. This variable is deprecated along with INSERT DELAYED.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(239, 'mysql', 'delayed_queue_size', '1000', 1, '[1-4294967295]', 'What size queue (in rows) should be allocated for handling INSERT DELAYED. If the queue becomes full, any client that does INSERT DELAYED will wait until there is room in the queue again. This variable is deprecated along with INSERT DELAYED.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(240, 'mysql', 'delay_key_write', 'ON', 1, '[ON|OFF|ALL]', 'Type of DELAY_KEY_WRITE', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(241, 'mysql', 'disconnect_on_expired_password', 'ON', 0, '[ON|OFF]', 'This variable controls how the server handles clients with expired passwords', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(242, 'mysql', 'div_precision_increment', '4', 1, '[0-30]', 'Precision of the result of \'/\' operator will be increased on that value', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(243, 'mysql', 'end_markers_in_json', 'OFF', 1, '[ON|OFF]', 'Whether optimizer JSON output should add end markers. ', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(244, 'mysql', 'eq_range_index_dive_limit', '10', 1, '[0-4294967295]', 'The optimizer will use existing index statistics instead of doing index dives for equality ranges if the number of equality ranges for the index is larger than or equal to this number. If set to 0, index dives are always used.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(245, 'mysql', 'event_scheduler', 'OFF', 1, 'ON', 'Enable the event scheduler. Possible values are ON, OFF, and DISABLED (keep the event scheduler completely deactivated, it cannot be activated run-time)', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(246, 'mysql', 'explicit_defaults_for_timestamp', 'OFF', 1, '[ON|OFF]', 'This system variable determines whether the server enables certain nonstandard behaviors for default values and NULL-value handling in TIMESTAMP columns.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(248, 'mysql', 'flush_time', '0', 1, '[0-31536000]', 'If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and synchronize unflushed data to disk. This option is best used only on systems with minimal resources.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(249, 'mysql', 'ft_max_word_len', '84', 0, '[10-4294967295]', 'The maximum length of the word to be included in a MyISAM FULLTEXT index.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(250, 'mysql', 'ft_min_word_len', '4', 0, '[1-3600]', 'The minimum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(251, 'mysql', 'ft_query_expansion_limit', '20', 0, '[0-1000]', 'Number of best matches to use for query expansion', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(252, 'mysql', 'group_concat_max_len', '1024', 1, '[4-1844674407370954752]', 'The maximum length of the result of function GROUP_CONCAT()', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(253, 'mysql', 'host_cache_size', '644', 1, '[0-65535]', 'The size of the internal host cache (see Section 8.12.5.2, “DNS Lookup Optimization and the Host Cache”). Setting the size to 0 disables the host cache. Changing the cache size at runtime implicitly causes a FLUSH HOSTS operation to clear the host cache and truncate the host_cache table.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(254, 'mysql', 'innodb_adaptive_flushing', 'ON', 1, '[ON|OFF]', 'Specifies whether to dynamically adjust the rate of flushing dirty pages in the InnoDB buffer pool based on the workload. Adjusting the flush rate dynamically is intended to avoid bursts of I/O activity.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(255, 'mysql', 'innodb_adaptive_flushing_lwm', '10', 1, '[0-70]', 'Defines the low water mark representing percentage of redo log capacity at which adaptive flushing is enabled.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(256, 'mysql', 'innodb_adaptive_hash_index', 'ON', 1, '[ON|OFF]', 'Enable InnoDB adaptive hash index (enabled by default). Disable with --skip-innodb-adaptive-hash-index.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(257, 'mysql', 'innodb_adaptive_max_sleep_delay', '150000', 1, '[1-1000000]', 'Permits InnoDB to automatically adjust the value of innodb_thread_sleep_delay up or down according to the current workload. Any nonzero value enables automated, dynamic adjustment of the innodb_thread_sleep_delay value, up to the maximum value specified in the innodb_adaptive_max_sleep_delay option. The value represents the number of microseconds. This option can be useful in busy systems, with greater than 16 InnoDB threads. (In practice, it is most valuable for MySQL systems with hundreds or thousands of simultaneous connections.)', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(258, 'mysql', 'innodb_autoextend_increment', '64', 1, '[1-1000]', 'The increment size (in megabytes) for extending the size of an auto-extending InnoDB system tablespace file when it becomes full. The default value is 64. ', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(259, 'mysql', 'innodb_autoinc_lock_mode', '1', 0, '[0|1|2]', 'The AUTOINC lock modes supported by InnoDB: 0 => Old style AUTOINC locking (for backward compatibility), 1 => New style AUTOINC locking; 2 => No AUTOINC locking (unsafe for SBR)', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(260, 'mysql', 'innodb_buffer_pool_dump_at_shutdown', 'ON', 1, '[ON|OFF]', 'Specifies whether to record the pages cached in the InnoDB buffer pool when the MySQL server is shut down, to shorten the warmup process at the next restart. Typically used in combination with innodb_buffer_pool_load_at_startup. The innodb_buffer_pool_dump_pct option defines the percentage of most recently used buffer pool pages to dump.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(261, 'mysql', 'innodb_buffer_pool_dump_pct', '25', 1, '[1-100]', 'Specifies the percentage of the most recently used pages for each buffer pool to read out and dump. The range is 1 to 100. The default value is 25. For example, if there are 4 buffer pools with 100 pages each, and innodb_buffer_pool_dump_pct is set to 25, the 25 most recently used pages from each buffer pool are dumped.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(262, 'mysql', 'innodb_buffer_pool_instances', '1', 0, '[1-64]', 'The number of regions that the InnoDB buffer pool is divided into. For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. Each page that is stored in or read from the buffer pool is assigned to one of the buffer pool instances randomly, using a hashing function. Each buffer pool manages its own free lists, flush lists, LRUs, and all other data structures connected to a buffer pool, and is protected by its own buffer pool mutex.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(263, 'mysql', 'innodb_buffer_pool_load_at_startup', 'ON', 0, '[ON|OFF]', 'Specifies that, on MySQL server startup, the InnoDB buffer pool is automatically warmed up by loading the same pages it held at an earlier time. Typically used in combination with innodb_buffer_pool_dump_at_shutdown.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(264, 'mysql', 'innodb_change_buffering', 'all', 1, '[none|inserts|deletes|changes|purges|all]', 'Whether InnoDB performs change buffering, an optimization that delays write operations to secondary indexes so that the I/O operations can be performed sequentially. Permitted values are described in the following table.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(265, 'mysql', 'innodb_change_buffer_max_size', '25', 1, '[0-50]', 'Maximum size for the InnoDB change buffer, as a percentage of the total size of the buffer pool. You might increase this value for a MySQL server with heavy insert, update, and delete activity, or decrease it for a MySQL server with unchanging data used for reporting.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(266, 'mysql', 'innodb_checksum_algorithm', 'crc32', 1, '[innodb|crc32|none|strict_innodb|strict_crc32|strict_none]', 'Specifies how to generate and verify the checksum stored in the disk blocks of InnoDB tablespaces.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(267, 'mysql', 'innodb_cmp_per_index_enabled', 'OFF', 1, '[ON|OFF]', 'Enables per-index compression-related statistics in the INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX table. Because these statistics can be expensive to gather, only enable this option on development, test, or slave instances during performance tuning related to InnoDB compressed tables.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(268, 'mysql', 'innodb_commit_concurrency', '0', 0, '[0-1000]', 'The number of threads that can commit at the same time. A value of 0 (the default) permits any number of transactions to commit simultaneously.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(269, 'mysql', 'innodb_compression_failure_threshold_pct', '5', 1, '[0-100]', 'Defines the compression failure rate threshold for a table, as a percentage, at which point MySQL begins adding padding within compressed pages to avoid expensive compression failures. When this threshold is passed, MySQL begins to leave additional free space within each new compressed page, dynamically adjusting the amount of free space up to the percentage of page size specified by innodb_compression_pad_pct_max. A value of zero disables the mechanism that monitors compression efficiency and dynamically adjusts the padding amount.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(270, 'mysql', 'innodb_compression_level', '6', 1, '[0-9]', 'Specifies the level of zlib compression to use for InnoDB compressed tables and indexes. A higher value lets you fit more data onto a storage device, at the expense of more CPU overhead during compression. A lower value lets you reduce CPU overhead when storage space is not critical, or you expect the data is not especially compressible.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(271, 'mysql', 'innodb_compression_pad_pct_max', '50', 1, '[0-70]', 'Specifies the maximum percentage that can be reserved as free space within each compressed page, allowing room to reorganize the data and modification log within the page when a compressed table or index is updated and the data might be recompressed. Only applies when innodb_compression_failure_threshold_pct is set to a nonzero value, and the rate of compression failures passes the cutoff point.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(272, 'mysql', 'innodb_concurrency_tickets', '5000', 1, '[1-4294967295]', 'Number of times a thread is allowed to enter InnoDB within the same SQL query after it has once got the ticket', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(273, 'mysql', 'innodb_deadlock_detect', 'ON', 1, '[ON|OFF]', 'This option is used to disable deadlock detection. On high concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. At times, it may be more efficient to disable deadlock detection and rely on the innodb_lock_wait_timeout setting for transaction rollback when a deadlock occurs.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(274, 'mysql', 'innodb_disable_sort_file_cache', 'ON', 1, '[ON|OFF]', 'if ON, disable page cache when innodb using sort file', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(275, 'mysql', 'innodb_flush_method', 'O_DIRECT', 0, '[fsync|O_DSYNC|littlesync|nosync|O_DIRECT|O_DIRECT_NO_FSYNC]', 'Defines the method used to flush data to InnoDB data files and log files, which can affect I/O throughput.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(276, 'mysql', 'innodb_flush_neighbors', '1', 1, '[0|1|2]', 'Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(277, 'mysql', 'innodb_flush_sync', 'ON', 1, '[ON|OFF]', 'The innodb_flush_sync parameter, which is enabled by default, causes the innodb_io_capacity setting to be ignored for bursts of I/O activity that occur at checkpoints. To adhere to the limit on InnoDB background I/O activity defined by the innodb_io_capacity setting, disable innodb_flush_sync.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(278, 'mysql', 'innodb_ft_cache_size', '8000000', 0, '[1600000-80000000]', 'The memory allocated, in bytes, for the InnoDB FULLTEXT search index cache, which holds a parsed document in memory while creating an InnoDB FULLTEXT index. Index inserts and updates are only committed to disk when the innodb_ft_cache_size size limit is reached. innodb_ft_cache_size defines the cache size on a per table basis.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(279, 'mysql', 'innodb_ft_enable_diag_print', 'OFF', 1, '[ON|OFF]', 'Whether to enable additional full-text search (FTS) diagnostic output. This option is primarily intended for advanced FTS debugging and will not be of interest to most users. Output is printed to the error log and includes information', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(280, 'mysql', 'innodb_ft_enable_stopword', 'ON', 1, '[ON|OFF]', 'Specifies that a set of stopwords is associated with an InnoDB FULLTEXT index at the time the index is created. If the innodb_ft_user_stopword_table option is set, the stopwords are taken from that table. Else, if the innodb_ft_server_stopword_table option is set, the stopwords are taken from that table. Otherwise, a built-in set of default stopwords is used.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(281, 'mysql', 'innodb_ft_max_token_size', '84', 0, '[10-84]', 'InnoDB Fulltext search maximum token size in characters', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(282, 'mysql', 'innodb_ft_min_token_size', '3', 0, '[0-16]', 'InnoDB Fulltext search minimum token size in characters', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(283, 'mysql', 'innodb_ft_num_word_optimize', '2000', 1, '[0-10000]', 'Number of words to process during each OPTIMIZE TABLE operation on an InnoDB FULLTEXT index. Because a bulk insert or update operation to a table containing a full-text search index could require substantial index maintenance to incorporate all changes, you might do a series of OPTIMIZE TABLE statements, each picking up where the last left off.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(284, 'mysql', 'innodb_ft_result_cache_limit', '2000000000', 1, '[1000000-4294967295]', 'The InnoDB full-text search query result cache limit (defined in bytes) per full-text search query or per thread. Intermediate and final InnoDB full-text search query results are handled in memory. Use innodb_ft_result_cache_limit to place a size limit on the full-text search query result cache to avoid excessive memory consumption in case of very large InnoDB full-text search query results (millions or hundreds of millions of rows, for example). Memory is allocated as required when a full-text search query is processed. If the result cache size limit is reached, an error is returned indicating that the query exceeds the maximum allowed memory.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(285, 'mysql', 'innodb_ft_sort_pll_degree', '2', 0, '[1-16]', 'Number of threads used in parallel to index and tokenize text in an InnoDB FULLTEXT index when building a search index.', '2019-04-08 01:54:41.000000', '2019-04-08 01:54:41.000000'),
(286, 'mysql', 'innodb_ft_total_cache_size', '640000000', 0, '[32000000-1600000000]', 'The total memory allocated, in bytes, for the InnoDB full-text search index cache for all tables. Creating numerous tables, each with a FULLTEXT search index, could consume a significant portion of available memory. innodb_ft_total_cache_size defines a global memory limit for all full-text search indexes to help avoid excessive memory consumption. If the global limit is reached by an index operation, a forced sync is triggered.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(287, 'mysql', 'innodb_io_capacity', '2000', 1, '[100-4294967295]', 'The innodb_io_capacity parameter sets an upper limit on the number of I/O operations performed per second by InnoDB background tasks, such as flushing pages from the buffer pool and merging data from the change buffer.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(288, 'mysql', 'innodb_io_capacity_max', '4000', 1, '[100-4294967295]', 'If flushing activity falls behind, InnoDB can flush more aggressively than the limit imposed by innodb_io_capacity. innodb_io_capacity_max defines an upper limit the number of I/O operations performed per second by InnoDB background tasks in such situations.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(289, 'mysql', 'innodb_large_prefix', 'OFF', 1, '[ON|OFF]', 'Support large index prefix length of REC_VERSION_56_MAX_INDEX_COL_LEN (3072) bytes.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(290, 'mysql', 'innodb_lock_wait_timeout', '50', 1, '[1-1073741824]', 'Timeout in seconds an InnoDB transaction may wait for a lock before being rolled back. Values above 100000000 disable the timeout.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(291, 'mysql', 'innodb_log_checksums', 'ON', 1, '[ON|OFF]', 'Enables or disables checksums for redo log pages. innodb_log_checksums replaces innodb_log_checksum_algorithm.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(292, 'mysql', 'innodb_log_compressed_pages', 'OFF', 1, '[ON|OFF]', 'Specifies whether images of re-compressed pages are written to the redo log. Re-compression may occur when changes are made to compressed data.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(293, 'mysql', 'innodb_lru_scan_depth', '1024', 1, '[100-4294967295]', 'A parameter that influences the algorithms and heuristics for the flush operation for the InnoDB buffer pool. Primarily of interest to performance experts tuning I/O-intensive workloads. It specifies, per buffer pool instance, how far down the buffer pool LRU page list the page cleaner thread scans looking for dirty pages to flush. This is a background operation performed once per second.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(294, 'mysql', 'innodb_max_dirty_pages_pct', '75', 1, '[50-90]', 'Percentage of dirty pages allowed in bufferpool.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(295, 'mysql', 'innodb_max_dirty_pages_pct_lwm', '0', 1, '[0-75]', 'Defines a low water mark representing the percentage of dirty pages at which preflushing is enabled to control the dirty page ratio. The default of 0 disables the pre-flushing behavior entirely', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(296, 'mysql', 'innodb_max_purge_lag', '0', 1, '[0-4294967295]', 'Defines the maximum length of the purge queue. The default value of 0 indicates no limit (no delays).', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(297, 'mysql', 'innodb_max_purge_lag_delay', '0', 1, '[0-10000000]', 'Specifies the maximum delay in microseconds for the delay imposed by theinnodb_max_purge_lag configuration option. A nonzero value represents an upper limit on the delay period computed from the formula based on the value of innodb_max_purge_lag. The default of zero means that there is no upper limit imposed on the delay interval.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(298, 'mysql', 'innodb_max_undo_log_size', '1073741824', 1, '[10485760-18446744073709551615]', 'Defines a threshold size for undo tablespaces. If an undo tablespace exceeds the threshold, it can be marked for truncation when innodb_undo_log_truncate is enabled. The default value is 1073741824 bytes (1024 MiB).', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(299, 'mysql', 'innodb_monitor_disable', '', 1, 'all', 'Disables InnoDB metrics counters. Counter data may be queried using the INFORMATION_SCHEMA.INNODB_METRICS table.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(300, 'mysql', 'innodb_monitor_enable', '', 1, 'all', 'innodb_monitor_enable', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(301, 'mysql', 'innodb_old_blocks_pct', '37', 1, '[5-95]', 'Percentage of the buffer pool to reserve for \'old\' blocks.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(302, 'mysql', 'innodb_old_blocks_time', '1000', 1, '[0-1024]', 'Move blocks to the \'new\' end of the buffer pool if the first access was at least this many milliseconds ago. The timeout is disabled if 0.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(303, 'mysql', 'innodb_online_alter_log_max_size', '134217728', 1, '[134217728-2147483647]', 'Maximum modification log file size for online index creation', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(304, 'mysql', 'innodb_open_files', '3000', 0, '[1-8192]', 'How many files at the maximum InnoDB keeps open at the same time.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(305, 'mysql', 'innodb_optimize_fulltext_only', 'OFF', 1, '[ON|OFF]', 'Changes the way OPTIMIZE TABLE operates on InnoDB tables. Intended to be enabled temporarily, during maintenance operations for InnoDB tables with FULLTEXT indexes.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(306, 'mysql', 'innodb_page_cleaners', '1', 0, '[1-64]', 'The number of page cleaner threads that flush dirty pages from buffer pool instances. Page cleaner threads perform flush list and LRU flushing. A single page cleaner thread was introduced in MySQL 5.6 to offload buffer pool flushing work from the InnoDB master thread. In MySQL 5.7, InnoDB provides support for multiple page cleaner threads. A value of 1 maintains the pre-MySQL 5.7 configuration in which there is a single page cleaner thread. When there are multiple page cleaner threads, buffer pool flushing tasks for each buffer pool instance are dispatched to idle page cleaner threads. The innodb_page_cleaners default value was changed from 1 to 4 in MySQL 5.7. If the number of page cleaner threads exceeds the number of buffer pool instances', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(307, 'mysql', 'innodb_print_all_deadlocks', 'OFF', 1, '[OFF|ON]', 'Print all deadlocks to MySQL error log (off by default)', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(308, 'mysql', 'innodb_purge_batch_size', '300', 0, '[1-5000]', 'Number of UNDO log pages to purge in one batch from the history list.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(309, 'mysql', 'innodb_purge_rseg_truncate_frequency', '128', 1, '[1-128]', 'Defines the frequency with which the purge system frees rollback segments in terms of the number of times that purge is invoked. An undo tablespace cannot be truncated until its rollback segments are freed. Normally, the purge system frees rollback segments once every 128 times that purge is invoked. The default value is 128. Reducing this value increases the frequency with which the purge thread frees rollback segments.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(310, 'mysql', 'innodb_purge_threads', '1', 0, '[1-32]', 'Purge threads can be from 1 to 32. Default is 4.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(311, 'mysql', 'innodb_random_read_ahead', 'OFF', 1, '[ON|OFF]', 'Enables the random read-ahead technique for optimizing InnoDB I/O.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(312, 'mysql', 'innodb_read_ahead_threshold', '56', 1, '[0-64]', 'Number of pages that must be accessed sequentially for InnoDB to trigger a readahead.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(313, 'mysql', 'innodb_read_io_threads', '4', 0, '[1-64]', 'Number of background read I/O threads in InnoDB.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(314, 'mysql', 'innodb_rollback_on_timeout', 'OFF', 0, '[OFF|ON]', 'Roll back the complete transaction on lock wait timeout, for 4.x compatibility (disabled by default)', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(315, 'mysql', 'innodb_rollback_segments', '128', 1, '[1-128]', 'Defines the number of rollback segments used by InnoDB.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(316, 'mysql', 'innodb_sort_buffer_size', '1048576', 0, '[65536-67108864]', 'Specifies the size of sort buffers used to sort data during creation of an InnoDB index. The specified size defines the amount of data that is read into memory for internal sorting and then written out to disk. This process is referred to as a “run”. During the merge phase, pairs of buffers of the specified size are read in and merged. The larger the setting, the fewer runs and merges there are.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(317, 'mysql', 'innodb_spin_wait_delay', '30', 1, '[0-4294967295]', 'The maximum delay between polls for a spin lock. The low-level implementation of this mechanism varies depending on the combination of hardware and operating system, so the delay does not correspond to a fixed time interval. For more information, see Section 14.6.10, “Configuring Spin Lock Polling”.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(318, 'mysql', 'innodb_stats_auto_recalc', 'ON', 1, '[ON|OFF]', 'Causes InnoDB to automatically recalculate persistent statistics after the data in a table is changed substantially. The threshold value is 10% of the rows in the table. This setting applies to tables created when the innodb_stats_persistent option is enabled. Automatic statistics recalculation may also be configured by specifying STATS_PERSISTENT=1 in a CREATE TABLE or ALTER TABLE statement. The amount of data sampled to produce the statistics is controlled by the innodb_stats_persistent_sample_pages configuration option.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(319, 'mysql', 'innodb_stats_method', 'nulls_equal', 1, '[nulls_equal|nulls_unequal|nulls_ignored]', 'Specifies how InnoDB index statistics collection code should treat NULLs. Possible values are NULLS_EQUAL (default), NULLS_UNEQUAL and NULLS_IGNORED', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(320, 'mysql', 'innodb_stats_on_metadata', 'OFF', 1, '[ON|OFF]', 'Enable statistics gathering for metadata commands such as SHOW TABLE STATUS for tables that use transient statistics (off by default)', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(321, 'mysql', 'innodb_stats_persistent', 'ON', 1, '[ON|OFF]', 'Specifies whether InnoDB index statistics are persisted to disk. Otherwise, statistics may be recalculated frequently which can lead to variations in query execution plans. This setting is stored with each table when the table is created. You can set innodb_stats_persistent at the global level before creating a table, or use the STATS_PERSISTENT clause of the CREATE TABLE and ALTER TABLE statements to override the system-wide setting and configure persistent statistics for individual tables.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(322, 'mysql', 'innodb_stats_persistent_sample_pages', '20', 1, '[0-4294967295]', 'The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE. Increasing the value improves the accuracy of index statistics, which can improve the query execution plan, at the expense of increased I/O during the execution of ANALYZE TABLE for an InnoDB table.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(323, 'mysql', 'innodb_stats_sample_pages', '8', 1, '[1-4294967296]', 'Deprecated, use innodb_stats_transient_sample_pages instead', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(324, 'mysql', 'innodb_stats_transient_sample_pages', '8', 1, '[1-4294967295]', 'The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE. The default value is 8. Increasing the value improves the accuracy of index statistics, which can improve the query execution plan, at the expense of increased I/O when opening an InnoDB table or recalculating statistics.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(325, 'mysql', 'innodb_status_output', 'OFF', 1, '[ON|OFF]', 'Enables or disables periodic output for the standard InnoDB Monitor. Also used in combination with innodb_status_output_locks to enable or disable periodic output for the InnoDB Lock Monitor.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(326, 'mysql', 'innodb_status_output_locks', 'OFF', 1, '[ON|OFF]', 'Enables or disables the InnoDB Lock Monitor. When enabled, the InnoDB Lock Monitor prints additional information about locks in SHOW ENGINE INNODB STATUS output and in periodic output printed to the MySQL error log. Periodic output for the InnoDB Lock Monitor is printed as part of the standard InnoDB Monitor output. The standard InnoDB Monitor must therefore be enabled for the InnoDB Lock Monitor to print data to the MySQL error log periodically.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(327, 'mysql', 'innodb_strict_mode', 'OFF', 1, '[ON|OFF]', 'Use strict mode when evaluating create options.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(328, 'mysql', 'innodb_sync_array_size', '1', 0, '[1-1024]', 'Defines the size of the mutex/lock wait array. Increasing the value splits the internal data structure used to coordinate threads, for higher concurrency in workloads with large numbers of waiting threads. This setting must be configured when the MySQL instance is starting up, and cannot be changed afterward. Increasing the value is recommended for workloads that frequently produce a large number of waiting threads, typically greater than 768.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(329, 'mysql', 'innodb_sync_spin_loops', '100', 1, '[0-4294967295]', 'The number of times a thread waits for an InnoDB mutex to be freed before the thread is suspended.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(330, 'mysql', 'innodb_table_locks', 'ON', 1, '[ON|OFF]', 'Enable InnoDB locking in LOCK TABLES', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(331, 'mysql', 'innodb_thread_concurrency', '0', 1, '[0-128]', 'Helps in performance tuning in heavily concurrent environments. Sets the maximum number of threads allowed inside InnoDB. Value 0 will disable the thread throttling.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(332, 'mysql', 'innodb_thread_sleep_delay', '10000', 1, '[1-3600000]', 'Time of innodb thread sleeping before joining InnoDB queue (usec). Value 0 disable a sleep', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(333, 'mysql', 'innodb_write_io_threads', '4', 0, '[1-64]', 'Number of background write I/O threads in InnoDB.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(334, 'mysql', 'interactive_timeout', '7200', 1, '[10-86400]', 'The number of seconds the server waits for activity on an interactive connection before closing it', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(335, 'mysql', 'join_buffer_size', '262144', 1, '[128-4294967295]', 'The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use indexes and thus perform full table scans.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(336, 'mysql', 'key_cache_age_threshold', '300', 1, '[100-4294967295]', 'This characterizes the number of hits a hot block has to be untouched until it is considered aged enough to be downgraded to a warm block. This specifies the percentage ratio of that number of hits to the total number of blocks in key cache', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(337, 'mysql', 'key_cache_block_size', '1024', 1, '[512-16384]', 'The default size of key cache blocks', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(338, 'mysql', 'key_cache_division_limit', '100', 1, '[1-100]', 'The minimum percentage of warm blocks in key cache', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(339, 'mysql', 'lc_time_names', 'en_US', 1, '[ja_JP|pt_BR|en_US]', 'This variable specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the DATE_FORMAT(), DAYNAME() and MONTHNAME() functions. Locale names are POSIX-style values such as \'ja_JP\' or \'pt_BR\'. The default value is \'en_US\' regardless of your system\'s locale setting.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(340, 'mysql', 'lock_wait_timeout', '31536000', 1, '[1-1073741824]', 'This variable specifies the timeout in seconds for attempts to acquire metadata locks. The permissible values range from 1 to 31536000 (1 year). The default is 31536000.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(341, 'mysql', 'log_queries_not_using_indexes', 'OFF', 1, '[ON|OFF]', 'Log queries that are executed without benefit of any index to the slow log if it is open', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(342, 'mysql', 'log_throttle_queries_not_using_indexes', '0', 1, '[0-4294967295]', 'If log_queries_not_using_indexes is enabled, the log_throttle_queries_not_using_indexes variable limits the number of such queries per minute that can be written to the slow query log. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(343, 'mysql', 'long_query_time', '1', 1, '[0.03-31536000]', 'Log all queries that have taken more than long_query_time seconds to execute to file. The argument will be treated as a decimal value with microsecond precision', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(344, 'mysql', 'loose_optimizer_trace', 'enabled=off,one_line=off', 1, '.*', 'The optimizer_trace system variable has these on/off switches,enabled,one_line', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(345, 'mysql', 'loose_optimizer_trace_features', 'greedy_search=on,range_optimizer=on,dynamic_range=on,repeated_subselect=on', 1, '.*', 'Those features can be excluded from tracing using the optimizer_trace_features system variable', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(346, 'mysql', 'loose_thread_handling', '"one-thread-per-connection"', 0, 'one-thread-per-connection', 'Define threads usage for handling queries, one of one-thread-per-connection, no-threads, loaded-dynamically', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(347, 'mysql', 'loose_thread_pool_oversubscribe', '10', 1, '', '', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(348, 'mysql', 'loose_thread_pool_stall_limit', '30', 1, '', '', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(349, 'mysql', 'loose_validate_password_length', '8', 1, '[1-12]', 'The minimum number of characters that validate_password requires passwords to have. This variable is unavailable unless validate_password is installed.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(350, 'mysql', 'low_priority_updates', '0', 1, '[0|1]', 'INSERT/DELETE/UPDATE has lower priority than selects', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(351, 'mysql', 'master_verify_checksum', 'OFF', 1, '[ON|OFF]', 'Enabling this variable causes the master to examine checksums when reading from the binary log. master_verify_checksum is disabled by default.in this case, the master uses the event length from the binary log to verify events, so that only complete events are read from the binary log.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(352, 'mysql', 'max_allowed_packet', '1073741824', 1, '[16384-1073741824]', 'The packet message buffer is initialized to net_buffer_length bytes, but can grow up to max_allowed_packet bytes when needed. This value by default is small, to catch large (possibly incorrect) packets.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(353, 'mysql', 'max_binlog_stmt_cache_size', '18446744073709547520', 1, '[4096-18446744073709547520]', 'If nontransactional statements within a transaction require more than this many bytes of memory, the server generates an error. The minimum value is 4096. The maximum and default values are 4GB on 32-bit platforms and 16EB (exabytes) on 64-bit platforms.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(354, 'mysql', 'max_connect_errors', '100', 1, '[1-4294967295]', 'If there is more than this number of interrupted connections from a host this host will be blocked from further connections', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(355, 'mysql', 'max_error_count', '64', 1, '[0-65535]', 'The maximum number of error, warning, and information messages to be stored for display by the SHOW ERRORS and SHOW WARNINGS statements. This is the same as the number of condition areas in the diagnostics area, and thus the number of conditions that can be inspected by GET DIAGNOSTICS.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(356, 'mysql', 'max_heap_table_size', '67108864', 1, '[16384-1844674407370954752]', 'This variable sets the maximum size to which user-created MEMORY tables are permitted to grow. The value of the variable is used to calculate MEMORY table MAX_ROWS values. Setting this variable has no effect on any existing MEMORY table, unless the table is re-created with a statement such as CREATE TABLE or altered with ALTER TABLE or TRUNCATE TABLE. A server restart also sets the maximum size of existing MEMORY tables to the global max_heap_table_size value.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(357, 'mysql', 'max_join_size', '18446744073709551615', 1, '[1-18446744073709551615]', 'Do not permit statements that probably need to examine more than max_join_size rows (for single-table statements) or row combinations (for multiple-table statements) or that are likely to do more than max_join_size disk seeks. By setting this value, you can catch statements where keys are not used properly and that would probably take a long time. Set it if your users tend to perform joins that lack a WHERE clause, that take a long time, or that return millions of rows.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(358, 'mysql', 'max_length_for_sort_data', '1024', 1, '[0-838860]', 'Max number of bytes in sorted records', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(359, 'mysql', 'max_points_in_geometry', '65536', 1, '[3-1048576]', 'The maximum value of the points_per_circle argument to the ST_Buffer_Strategy() function.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(360, 'mysql', 'max_prepared_stmt_count', '16382', 1, '[0-1048576]', 'Maximum number of prepared statements in the server', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(361, 'mysql', 'max_seeks_for_key', '18446744073709500000', 1, '[1-18446744073709551615]', 'Limit the assumed maximum number of seeks when looking up rows based on a key. The MySQL optimizer assumes that no more than this number of key seeks are required when searching for matching rows in a table by scanning an index, regardless of the actual cardinality of the index. By setting this to a low value (say, 100), you can force MySQL to prefer indexes instead of table scans.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(362, 'mysql', 'max_sort_length', '1024', 1, '[4-8388608]', 'The number of bytes to use when sorting data values. The server uses only the first max_sort_length bytes of each value and ignores the rest. Consequently, values that differ only after the first max_sort_length bytes compare as equal for GROUP BY, ORDER BY, and DISTINCT operations.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(363, 'mysql', 'max_sp_recursion_depth', '0', 1, '[0-255]', 'The number of times that any given stored procedure may be called recursively. The default value for this option is 0, which completely disables recursion in stored procedures. The maximum value is 255.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(364, 'mysql', 'max_write_lock_count', '102400', 1, '[1-102400]', 'After this many write locks, allow some read locks to run in between', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(365, 'mysql', 'metadata_locks_cache_size', '1024', 0, '[1-1048576]', 'The size of the metadata locks cache. The server uses this cache to avoid creation and destruction of synchronization objects. This is particularly helpful on systems where such operations are expensive, such as Windows XP.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(366, 'mysql', 'min_examined_row_limit', '0', 1, '[0-4294967295]', 'Queries that examine fewer than this number of rows are not logged to the slow query log.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(367, 'mysql', 'myisam_sort_buffer_size', '262144', 1, '[262144-16777216]', 'The buffer that is allocated when sorting the index when doing a REPAIR or when creating indexes with CREATE INDEX or ALTER TABLE', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(368, 'mysql', 'mysql_native_password_proxy_users', 'OFF', 1, '[ON|OFF]', 'This variable controls whether the mysql_native_password built-in authentication plugin supports proxy users. It has no effect unless the check_proxy_users system variable is enabled. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(369, 'mysql', 'net_buffer_length', '16384', 1, '[1024-1048576]', 'Each client thread is associated with a connection buffer and result buffer. Both begin with a size given by net_buffer_length but are dynamically enlarged up to max_allowed_packet bytes as needed. The result buffer shrinks to net_buffer_length after each SQL statement.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(370, 'mysql', 'net_read_timeout', '30', 1, '[1-31536000]', 'Number of seconds to wait for more data from a connection before aborting the read', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(371, 'mysql', 'net_retry_count', '10', 1, '[1-4294967295]', 'If a read on a communication port is interrupted, retry this many times before giving up', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(372, 'mysql', 'net_write_timeout', '60', 1, '[1-31536000]', 'Number of seconds to wait for a block to be written to a connection before aborting the write', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(373, 'mysql', 'ngram_token_size', '2', 0, '[0-20]', 'Defines the n-gram token size for the n-gram full-text parser. The ngram_token_size option is read-only and can only be modified at startup. The default value is 2 (bigram). The maximum value is 10.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(374, 'mysql', 'old_passwords', '0', 1, '[0|2]', 'This variable controls the password hashing method used by the PASSWORD() function. It also influences password hashing performed by CREATE USER and GRANT statements that specify a password using an IDENTIFIED BY clause', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(375, 'mysql', 'open_files_limit', '65535', 0, '[4000-65535]', 'If this is not 0, then mysqld will use this value to reserve file descriptors to use with setrlimit(). If this value is 0 then mysqld will reserve max_connections*5 or max_connections + table_open_cache*2 (whichever is larger) number of file descriptors', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(376, 'mysql', 'optimizer_prune_level', '1', 1, '[0|1]', 'Controls the heuristics applied during query optimization to prune less-promising partial plans from the optimizer search space. A value of 0 disables heuristics so that the optimizer performs an exhaustive search. A value of 1 causes the optimizer to prune plans based on the number of rows retrieved by intermediate plans.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(377, 'mysql', 'optimizer_search_depth', '62', 1, '[0-62]', 'The maximum depth of search performed by the query optimizer. Values larger than the number of relations in a query result in better query plans, but take longer to generate an execution plan for a query. Values smaller than the number of relations in a query return an execution plan quicker, but the resulting plan may be far from being optimal. If set to 0, the system automatically picks a reasonable value.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(378, 'mysql', 'optimizer_trace_limit', '1', 1, '[0-4294967295]', 'The maximum number of optimizer traces to display. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(379, 'mysql', 'optimizer_trace_max_mem_size', '16384', 1, '[0-4294967295]', 'The maximum cumulative size of stored optimizer traces. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(380, 'mysql', 'optimizer_trace_offset', '-1', 1, '[0-4294967295]', 'The offset of optimizer traces to display.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(381, 'mysql', 'performance_schema', 'OFF', 0, '[ON|OFF]', 'Enable the performance schema.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(382, 'mysql', 'preload_buffer_size', '32768', 1, '[1024-1073741824]', 'The size of the buffer that is allocated when preloading indexes.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(383, 'mysql', 'query_alloc_block_size', '8192', 1, '[1024-16384]', 'Allocation block size for query parsing and execution', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(384, 'mysql', 'query_cache_limit', '1048576', 1, '[1-1048576]', 'Don\'t cache results that are bigger than this', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(385, 'mysql', 'query_cache_min_res_unit', '1024', 1, '[512-18446744073709551608]', 'The minimum size (in bytes) for blocks allocated by the query cache. The default value is 4096 (4KB).', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(386, 'mysql', 'query_cache_size', '3145728', 1, '[0-104857600]', 'The memory allocated to store results from old queries', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(387, 'mysql', 'query_cache_type', '0', 0, '[0|1|2]', 'OFF = Don\'t cache or retrieve results. ON = Cache all results except SELECT SQL_NO_CACHE ... queries. DEMAND = Cache only SELECT SQL_CACHE ... queries', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(388, 'mysql', 'query_cache_wlock_invalidate', 'OFF', 1, '[ON|OFF]', 'Normally, when one client acquires a WRITE lock on a MyISAM table, other clients are not blocked from issuing statements that read from the table if the query results are present in the query cache. Setting this variable to 1 causes acquisition of a WRITE lock for a table to invalidate any queries in the query cache that refer to the table. This forces other clients that attempt to access the table to wait while the lock is in effect.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(389, 'mysql', 'query_prealloc_size', '8192', 1, '[8192-1048576]', 'Persistent buffer for query parsing and execution', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(390, 'mysql', 'range_alloc_block_size', '4096', 1, '[4096-18446744073709551615]', 'The size of blocks that are allocated when doing range optimization.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(391, 'mysql', 'range_optimizer_max_mem_size', '8388608', 0, '[0-18446744073709551615]', 'The limit on memory consumption for the range optimizer. A value of 0 means “no limit.” If an execution plan considered by the optimizer uses the range access method but the optimizer estimates that the amount of memory needed for this method would exceed the limit, it abandons the plan and considers other plans. For more information, see Limiting Memory Use for Range Optimization.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(392, 'mysql', 'session_track_gtids', 'OFF', 1, '[OFF|OWN_GTID|ALL_GTIDS]OFF', 'Controls a tracker for capturing GTIDs and returning them in the OK packet. Depending on the value of this option, at the end of executing a transaction, the GTIDs specified are captured by the tracker and appended to the OK packet.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(393, 'mysql', 'session_track_schema', 'ON', 1, '[ON|OFF]', 'Controls whether the server tracks changes to the default schema (database) name within the current session and makes this information available to the client when changes occur.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(394, 'mysql', 'session_track_state_change', 'OFF', 1, '[ON|OFF]', 'Controls whether the server tracks changes to the state of the current session and notifies the client when state changes occur. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(395, 'mysql', 'sha256_password_proxy_users', 'OFF', 1, '[ON|OFF]', 'This variable controls whether the sha256_password built-in authentication plugin supports proxy users. It has no effect unless the check_proxy_users system variable is enabled.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(396, 'mysql', 'show_compatibility_56', 'OFF', 1, '[ON|OFF]', 'The INFORMATION_SCHEMA has tables that contain system and status variable information The Performance Schema tables are intended to replace the INFORMATION_SCHEMA tables, which are deprecated as of MySQL 5.7.6 and will be removed in a future MySQL release.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(397, 'mysql', 'show_old_temporals', 'OFF', 1, '[ON|OFF]', 'Whether SHOW CREATE TABLE output includes comments to flag temporal columns found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). This variable is disabled by default. If enabled', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(398, 'mysql', 'slave_net_timeout', '60', 1, '[15-300]', 'The number of seconds to wait for more data from the master before the slave considers the connection broken, aborts the read, and tries to reconnect', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(399, 'mysql', 'slave_parallel_type', 'LOGICAL_CLOCK', 0, 'DATABASE,LOGICAL_CLOCK', 'Specifies if the slave will use database partitioning or information from master to parallelize transactions.(Default: DATABASE).', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(400, 'mysql', 'slow_launch_time', '2', 1, '[1-1024]', 'If creating the thread takes longer than this value (in seconds), the Slow_launch_threads counter will be incremented', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(401, 'mysql', 'slow_query_log', 'ON', 1, '[ON|OFF]', 'Specify the initial slow query log state. With no argument or an argument of 1, the --slow-query-log option enables the log. If omitted or given with an argument of 0, the option disables the log.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(402, 'mysql', 'sort_buffer_size', '262144', 1, '[32768-4294967295]', 'Each session that must perform a sort allocates a buffer of this size. ', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(403, 'mysql', 'sql_mode', '', 1, '(\\s*|REAL_AS_FLOAT|PIPES_AS_CONCAT|ANSI_QUOTES|IGNORE_SPACE|ONLY_FULL_GROUP_BY|NO_UNSIGNED_SUBTRACTION|NO_DIR_IN_CREATE|POSTGRESQL|ORACLE|MSSQL|DB2|MAXDB|NO_KEY_OPTIONS|NO_TABLE_OPTIONS|NO_FIELD_OPTIONS|MYSQL323|MYSQL40|ANSI|NO_AUTO_VALUE_ON_ZERO|NO_BACKSLASH_ESCAPES|STRICT_TRANS_TABLES|STRICT_ALL_TABLES|NO_ZERO_IN_DATE|NO_ZERO_DATE|ALLOW_INVALID_DATES|ERROR_FOR_DIVISION_BY_ZERO|TRADITIONAL|HIGH_NOT_PRECEDENCE|NO_ENGINE_SUBSTITUTION|PAD_CHAR_TO_FULL_LENGTH)(,REAL_AS_FLOAT|,PIPES_AS_CONCAT|,ANSI_QUOTES|,IGNORE_SPACE|,ONLY_FULL_GROUP_BY|,NO_UNSIGNED_SUBTRACTION|,NO_DIR_IN_CREATE|,POSTGRESQL|,ORACLE|,MSSQL|,DB2|,MAXDB|,NO_KEY_OPTIONS|,NO_TABLE_OPTIONS|,NO_FIELD_OPTIONS|,MYSQL323|,MYSQL40|,ANSI|,NO_AUTO_VALUE_ON_ZERO|,NO_BACKSLASH_ESCAPES|,STRICT_TRANS_TABLES|,STRICT_ALL_TABLES|,NO_ZERO_IN_DATE|,NO_ZERO_DATE|,ALLOW_INVALID_DATES|,ERROR_FOR_DIVISION_BY_ZERO|,TRADITIONAL|,HIGH_NOT_PRECEDENCE|,NO_ENGINE_SUBSTITUTION|,PAD_CHAR_TO_FULL_LENGTH)*', 'Syntax: sql-mode=mode[,mode[,mode...]]. See the manual for the complete list of valid sql modes', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(404, 'mysql', 'stored_program_cache', '256', 1, '[16-524288]', 'Sets a soft upper limit for the number of cached stored routines per connection. The value of this variable is specified in terms of the number of stored routines held in each of the two caches maintained by the MySQL Server for, respectively, stored procedures and stored functions.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(405, 'mysql', 'table_definition_cache', '512', 1, '[400-80480]', 'The number of cached table definitions', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(406, 'mysql', 'table_open_cache', '2000', 1, '[1-524288]', 'The number of cached open tables (total for all table cache instances)', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(407, 'mysql', 'table_open_cache_instances', '1', 0, '[1-64]', 'The number of open tables cache instances. To improve scalability by reducing contention among sessions, the open tables cache can be partitioned into several smaller cache instances of size table_open_cache / table_open_cache_instances . A session needs to lock only one instance to access it for DML statements. This segments cache access among instances, permitting higher performance for operations that use the cache when there are many sessions accessing tables. (DDL statements still require a lock on the entire cache, but such statements are much less frequent than DML statements.)', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(408, 'mysql', 'thread_cache_size', '100', 1, '[0-16384]', 'How many threads the server should cache for reuse. When a client disconnects, the client\'s threads are put in the cache if there are fewer than thread_cache_size threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. Normally, this does not provide a notable performance improvement if you have a good thread implementation. However, if your server sees hundreds of connections per second you should normally set thread_cache_size high enough so that most new connections use cached threads. By examining the difference between the Connections and Threads_created status variables, you can see how efficient the thread cache is.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(409, 'mysql', 'thread_stack', '262144', 0, '[131072-1073741824]', 'The stack size for each thread. The default of 192KB (256KB for 64-bit systems) is large enough for normal operation. If the thread stack size is too small, it limits the complexity of the SQL statements that the server can handle, the recursion depth of stored procedures, and other memory-consuming actions.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(410, 'mysql', 'tls_version', 'TLSv1,TLSv1.1,TLSv1.2', 0, '[TLSv1,TLSv1.1,TLSv1.2|TLSv1,TLSv1.1]', 'The protocols permitted by the server for encrypted connections. The value is a comma-separated list containing one or more protocol names. The protocols that can be named for this variable depend on the SSL library used to compile MySQL.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(411, 'mysql', 'tmp_table_size', '2097152', 1, '[262144-67108864]', 'If an internal in-memory temporary table exceeds this size, MySQL will automatically convert it to an on-disk MyISAM table', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(412, 'mysql', 'transaction_alloc_block_size', '8192', 1, '[1024-131072]', 'The amount in bytes by which to increase a per-transaction memory pool which needs memory. See the description of transaction_prealloc_size.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(413, 'mysql', 'transaction_isolation', 'READ-COMMITTED', 1, '[READ-UNCOMMITTED|READ-COMMITTED|REPEATABLE-READ|SERIALIZABLE]', 'Default transaction isolation level', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(414, 'mysql', 'transaction_prealloc_size', '4096', 1, '[1024-131072]', 'There is a per-transaction memory pool from which various transaction-related allocations take memory. The initial size of the pool in bytes is transaction_prealloc_size. For every allocation that cannot be satisfied from the pool because it has insufficient memory available, the pool is increased by transaction_alloc_block_size bytes. When the transaction ends, the pool is truncated to transaction_prealloc_size bytes.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(415, 'mysql', 'updatable_views_with_limit', 'YES', 1, '[YES|NO]', 'This variable controls whether updates to a view can be made when the view does not contain all columns of the primary key defined in the underlying table, if the update statement contains a LIMIT clause. (Such updates often are generated by GUI tools.) An update is an UPDATE or DELETE statement. Primary key here means a PRIMARY KEY, or a UNIQUE index in which no column can contain NULL.', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000'),
(416, 'mysql', 'wait_timeout', '86400', 1, '[1-31536000]', 'The number of seconds the server waits for activity on a connection before closing it', '2019-04-08 01:54:42.000000', '2019-04-08 01:54:42.000000');
-- 导出 表 htmltooarchery.query_log 结构
DROP TABLE IF EXISTS `query_log`;
CREATE TABLE IF NOT EXISTS `query_log` (
`id` int NOT NULL AUTO_INCREMENT,
`instance_name` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`db_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`sqllog` longtext COLLATE utf8mb4_general_ci NOT NULL,
`effect_row` bigint NOT NULL,
`cost_time` varchar(10) COLLATE utf8mb4_general_ci NOT NULL,
`username` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`priv_check` tinyint(1) NOT NULL,
`hit_rule` tinyint(1) NOT NULL,
`masking` tinyint(1) NOT NULL,
`favorite` tinyint(1) NOT NULL,
`alias` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.query_log 的数据：~0 rows (大约)
DELETE FROM `query_log`;
-- 导出 表 htmltooarchery.query_privileges 结构
DROP TABLE IF EXISTS `query_privileges`;
CREATE TABLE IF NOT EXISTS `query_privileges` (
`privilege_id` int NOT NULL AUTO_INCREMENT,
`user_name` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`db_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`table_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`valid_date` date NOT NULL,
`limit_num` int NOT NULL,
`priv_type` int NOT NULL,
`is_deleted` int NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`privilege_id`),
KEY `query_privileges_instance_id_047fcde2_fk_sql_instance_id` (`instance_id`),
KEY `query_privileges_user_name_instance_id_db__ed2ad8a3_idx` (`user_name`,`instance_id`,`db_name`,`valid_date`),
CONSTRAINT `query_privileges_instance_id_047fcde2_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.query_privileges 的数据：~0 rows (大约)
DELETE FROM `query_privileges`;
-- 导出 表 htmltooarchery.query_privileges_apply 结构
DROP TABLE IF EXISTS `query_privileges_apply`;
CREATE TABLE IF NOT EXISTS `query_privileges_apply` (
`apply_id` int NOT NULL AUTO_INCREMENT,
`group_id` int NOT NULL,
`group_name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`title` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`user_name` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`db_list` longtext COLLATE utf8mb4_general_ci NOT NULL,
`table_list` longtext COLLATE utf8mb4_general_ci NOT NULL,
`valid_date` date NOT NULL,
`limit_num` int NOT NULL,
`priv_type` int NOT NULL,
`status` int NOT NULL,
`audit_auth_groups` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`apply_id`),
KEY `query_privileges_apply_instance_id_bc03347f_fk_sql_instance_id` (`instance_id`),
CONSTRAINT `query_privileges_apply_instance_id_bc03347f_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.query_privileges_apply 的数据：~0 rows (大约)
DELETE FROM `query_privileges_apply`;
-- 导出 表 htmltooarchery.resource_group 结构
DROP TABLE IF EXISTS `resource_group`;
CREATE TABLE IF NOT EXISTS `resource_group` (
`group_id` int NOT NULL AUTO_INCREMENT,
`group_name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`group_parent_id` bigint NOT NULL,
`group_sort` int NOT NULL,
`group_level` int NOT NULL,
`ding_webhook` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`feishu_webhook` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`qywx_webhook` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`is_deleted` int NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`group_id`),
UNIQUE KEY `group_name` (`group_name`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.resource_group 的数据：~0 rows (大约)
DELETE FROM `resource_group`;
INSERT INTO `resource_group` (`group_id`, `group_name`, `group_parent_id`, `group_sort`, `group_level`, `ding_webhook`, `feishu_webhook`, `qywx_webhook`, `is_deleted`, `create_time`, `sys_time`) VALUES
(1, '测试组', 0, 1, 1, '', '', '', 0, '2023-11-14 15:54:37.819927', '2023-11-14 15:54:37.819975');
-- 导出 表 htmltooarchery.sql_config 结构
DROP TABLE IF EXISTS `sql_config`;
CREATE TABLE IF NOT EXISTS `sql_config` (
`id` int NOT NULL AUTO_INCREMENT,
`item` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`value` varchar(500) COLLATE utf8mb4_general_ci NOT NULL,
`description` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `item` (`item`)
) ENGINE=InnoDB AUTO_INCREMENT=498 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_config 的数据：~0 rows (大约)
DELETE FROM `sql_config`;
INSERT INTO `sql_config` (`id`, `item`, `value`, `description`) VALUES
(427, 'go_inception_host', '166VgDXgimhFHhljod4fDQ==', ''),
(428, 'go_inception_port', 'D_iAIoesr7mmjPtiaS5Qeg==', ''),
(429, 'inception_remote_backup_host', 'en2_vZJ6OZP7l0seO5-Iig==', ''),
(430, 'inception_remote_backup_port', 'gzj9jvgRHy5zl-GMtpamug==', ''),
(431, 'inception_remote_backup_user', 'tzxlKzuTvWfk-1HLCT_guw==', ''),
(432, 'inception_remote_backup_password', 'ix79fRFT-EYMi27dEgrlhA==', ''),
(433, 'critical_ddl_regex', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(434, 'auto_review_wrong', 'suwCkkNSpbcRAXNtf2cZ6g==', ''),
(435, 'enable_backup_switch', 'vFO44abhNH4MJdz3j7GvdA==', ''),
(436, 'auto_review', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(437, 'auto_review_tag', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(438, 'auto_review_db_type', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(439, 'auto_review_regex', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(440, 'auto_review_max_update_rows', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(441, 'manual', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(442, 'ddl_dml_separation', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(443, 'ban_self_audit', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(444, 'data_masking', 'vFO44abhNH4MJdz3j7GvdA==', ''),
(445, 'query_check', 'vFO44abhNH4MJdz3j7GvdA==', ''),
(446, 'disable_star', 'vFO44abhNH4MJdz3j7GvdA==', ''),
(447, 'max_execution_time', '5CLfxGJk4TEao_fNl836fA==', ''),
(448, 'admin_query_limit', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(449, 'sqladvisor', 'q8e6-_vUJSOu1mDqHKuKD50fEFljmKzQHV_zlYmII2N5fE2MkhmzjPVSKFaA2hK0', ''),
(450, 'soar', 'q8e6-_vUJSOu1mDqHKuKD4MrGzLDgsG0j2oG8Heh0Ys=', ''),
(451, 'soar_test_dsn', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(452, 'archery_base_url', 'zB91bIb6Qh83QH7C_5I4pZ1CQnJZXTwOz5xj5j_AX58=', ''),
(453, 'ddl_notify_auth_group', 'Xy4_hFjdd0THFFM7aaGRlA==', ''),
(454, 'notify_phase_control', 'zsS_zoOtEWPTOC8bI7GoXjcvgzH22cWEAteL6dTMUM0=', ''),
(455, 'mail', 'P5RfC56v4fDTr-ZDK1lSUQ==', ''),
(456, 'mail_ssl', 'P5RfC56v4fDTr-ZDK1lSUQ==', ''),
(457, 'mail_smtp_server', 'G5hteeIM9E30RVACCXMkbkjZf-bj2BklTH9FNsuomI4=', ''),
(458, 'mail_smtp_port', 'MMkjUNm9YQlVKjoc8YQz1g==', ''),
(459, 'mail_smtp_user', 'bEOpAb7LlhI8_5SWEjoXOdho7tBOy-DLbbgykROGpmo=', ''),
(460, 'mail_smtp_password', 'y_ilQusu2IqcppWIqFTDjAZyUlFycZYH-SvJZ76F6y4=', ''),
(461, 'ding', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(462, 'ding_to_person', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(463, 'ding_agent_id', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(464, 'ding_app_key', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(465, 'ding_app_secret', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(466, 'ding_archery_username', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(467, 'ding_dept_ids', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(468, 'wx', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(469, 'wx_corpid', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(470, 'wx_agent_id', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(471, 'wx_app_secret', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(472, 'qywx_webhook', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(473, 'feishu_webhook', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(474, 'feishu', 'P5RfC56v4fDTr-ZDK1lSUQ==', ''),
(475, 'feishu_appid', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(476, 'feishu_app_secret', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(477, 'sms_provider', 'anTWW2BE64m5bFEPZ-ZZXA==', ''),
(478, 'aliyun_access_key_id', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(479, 'aliyun_access_key_secret', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(480, 'aliyun_sign_name', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(481, 'aliyun_template_code', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(482, 'aliyun_variable_name', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(483, 'tencent_secret_id', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(484, 'tencent_secret_key', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(485, 'tencent_sign_name', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(486, 'tencent_template_id', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(487, 'tencent_sdk_appid', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(488, 'index_path_url', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(489, 'my2sql', 'q8e6-_vUJSOu1mDqHKuKD9eslIYWNo99FdA9HxB5Edw=', ''),
(490, 'default_auth_group', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(491, 'default_resource_group', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(492, 'api_user_whitelist', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(493, 'lock_time_threshold', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(494, 'lock_cnt_threshold', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(495, 'sign_up_enabled', 'BnJSUXJxlgf5K8lnvoXrLg==', ''),
(496, 'watermark_enabled', 'vFO44abhNH4MJdz3j7GvdA==', ''),
(497, 'enforce_2fa', 'P5RfC56v4fDTr-ZDK1lSUQ==', '');
-- 导出 表 htmltooarchery.sql_instance 结构
DROP TABLE IF EXISTS `sql_instance`;
CREATE TABLE IF NOT EXISTS `sql_instance` (
`id` int NOT NULL AUTO_INCREMENT,
`instance_name` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`type` varchar(6) COLLATE utf8mb4_general_ci NOT NULL,
`db_type` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`mode` varchar(10) COLLATE utf8mb4_general_ci NOT NULL,
`host` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`port` int NOT NULL,
`user` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`password` varchar(300) COLLATE utf8mb4_general_ci NOT NULL,
`db_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`charset` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`service_name` varchar(50) COLLATE utf8mb4_general_ci DEFAULT NULL,
`sid` varchar(50) COLLATE utf8mb4_general_ci DEFAULT NULL,
`create_time` datetime(6) NOT NULL,
`update_time` datetime(6) NOT NULL,
`tunnel_id` int DEFAULT NULL,
`is_ssl` tinyint(1) DEFAULT '0' COMMENT '是否启用SSL',
PRIMARY KEY (`id`),
UNIQUE KEY `instance_name` (`instance_name`),
KEY `sql_instance_tunnel_id_99377638_fk_ssh_tunnel_id` (`tunnel_id`),
CONSTRAINT `sql_instance_tunnel_id_99377638_fk_ssh_tunnel_id` FOREIGN KEY (`tunnel_id`) REFERENCES `ssh_tunnel` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_instance 的数据：~0 rows (大约)
DELETE FROM `sql_instance`;
INSERT INTO `sql_instance` (`id`, `instance_name`, `type`, `db_type`, `mode`, `host`, `port`, `user`, `password`, `db_name`, `charset`, `service_name`, `sid`, `create_time`, `update_time`, `tunnel_id`, `is_ssl`) VALUES
(1, 'mariadb', 'master', 'mysql', '', 'mariadb', 3306, 'mgc-Oh9sGUWwSFhtQFio4A==', 'arsTeNAkw_qOmdSJgGtoEA==', '', '', NULL, NULL, '2023-11-14 15:53:13.766697', '2023-11-14 15:53:13.766751', NULL, 0);
-- 导出 表 htmltooarchery.sql_instance_instance_tag 结构
DROP TABLE IF EXISTS `sql_instance_instance_tag`;
CREATE TABLE IF NOT EXISTS `sql_instance_instance_tag` (
`id` int NOT NULL AUTO_INCREMENT,
`instance_id` int NOT NULL,
`instancetag_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `sql_instance_instance_ta_instance_id_instancetag__2797cd96_uniq` (`instance_id`,`instancetag_id`),
KEY `sql_instance_instanc_instancetag_id_d18b0067_fk_sql_insta` (`instancetag_id`),
CONSTRAINT `sql_instance_instanc_instance_id_35a5a19d_fk_sql_insta` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`),
CONSTRAINT `sql_instance_instanc_instancetag_id_d18b0067_fk_sql_insta` FOREIGN KEY (`instancetag_id`) REFERENCES `sql_instance_tag` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_instance_instance_tag 的数据：~0 rows (大约)
DELETE FROM `sql_instance_instance_tag`;
-- 导出 表 htmltooarchery.sql_instance_resource_group 结构
DROP TABLE IF EXISTS `sql_instance_resource_group`;
CREATE TABLE IF NOT EXISTS `sql_instance_resource_group` (
`id` int NOT NULL AUTO_INCREMENT,
`instance_id` int NOT NULL,
`resourcegroup_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `sql_instance_resource_gr_instance_id_resourcegrou_0dbfb149_uniq` (`instance_id`,`resourcegroup_id`),
KEY `sql_instance_resourc_resourcegroup_id_1903be9b_fk_resource_` (`resourcegroup_id`),
CONSTRAINT `sql_instance_resourc_instance_id_30cfcc32_fk_sql_insta` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`),
CONSTRAINT `sql_instance_resourc_resourcegroup_id_1903be9b_fk_resource_` FOREIGN KEY (`resourcegroup_id`) REFERENCES `resource_group` (`group_id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_instance_resource_group 的数据：~0 rows (大约)
DELETE FROM `sql_instance_resource_group`;
INSERT INTO `sql_instance_resource_group` (`id`, `instance_id`, `resourcegroup_id`) VALUES
(1, 1, 1);
-- 导出 表 htmltooarchery.sql_instance_tag 结构
DROP TABLE IF EXISTS `sql_instance_tag`;
CREATE TABLE IF NOT EXISTS `sql_instance_tag` (
`id` int NOT NULL AUTO_INCREMENT,
`tag_code` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`tag_name` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`active` tinyint(1) NOT NULL,
`create_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `tag_code` (`tag_code`),
UNIQUE KEY `tag_name` (`tag_name`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_instance_tag 的数据：~0 rows (大约)
DELETE FROM `sql_instance_tag`;
INSERT INTO `sql_instance_tag` (`id`, `tag_code`, `tag_name`, `active`, `create_time`) VALUES
(1, 'can_write', '支持上线', 1, '2023-11-14 13:08:02.000000'),
(2, 'can_read', '支持查询', 1, '2023-11-14 13:08:02.000000');
-- 导出 表 htmltooarchery.sql_permission 结构
DROP TABLE IF EXISTS `sql_permission`;
CREATE TABLE IF NOT EXISTS `sql_permission` (
`id` int NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_permission 的数据：~0 rows (大约)
DELETE FROM `sql_permission`;
-- 导出 表 htmltooarchery.sql_users 结构
DROP TABLE IF EXISTS `sql_users`;
CREATE TABLE IF NOT EXISTS `sql_users` (
`id` int NOT NULL AUTO_INCREMENT,
`password` varchar(128) COLLATE utf8mb4_general_ci NOT NULL,
`last_login` datetime(6) DEFAULT NULL,
`is_superuser` tinyint(1) NOT NULL,
`username` varchar(150) COLLATE utf8mb4_general_ci NOT NULL,
`first_name` varchar(150) COLLATE utf8mb4_general_ci NOT NULL,
`last_name` varchar(150) COLLATE utf8mb4_general_ci NOT NULL,
`email` varchar(254) COLLATE utf8mb4_general_ci NOT NULL,
`is_staff` tinyint(1) NOT NULL,
`is_active` tinyint(1) NOT NULL,
`date_joined` datetime(6) NOT NULL,
`display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`ding_user_id` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`wx_user_id` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`feishu_open_id` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`failed_login_count` int NOT NULL,
`last_login_failed_at` datetime(6) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `username` (`username`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_users 的数据：~0 rows (大约)
DELETE FROM `sql_users`;
INSERT INTO `sql_users` (`id`, `password`, `last_login`, `is_superuser`, `username`, `first_name`, `last_name`, `email`, `is_staff`, `is_active`, `date_joined`, `display`, `ding_user_id`, `wx_user_id`, `feishu_open_id`, `failed_login_count`, `last_login_failed_at`) VALUES
(1, 'pbkdf2_sha256$390000$ZMfSNPirpCn3hqKSOJHW4q$i4h0m25+E3uhlQYFrk7dpVf1EFRQ50vKABfNfPLhoCk=', '2023-11-14 15:41:58.476434', 1, 'ihunter', '', '', 'ihunter@vip.qq.com', 1, 1, '2023-11-14 13:09:46.922848', '', '', '', '', 0, '2023-11-14 15:41:22.412099');
-- 导出 表 htmltooarchery.sql_users_groups 结构
DROP TABLE IF EXISTS `sql_users_groups`;
CREATE TABLE IF NOT EXISTS `sql_users_groups` (
`id` int NOT NULL AUTO_INCREMENT,
`users_id` int NOT NULL,
`group_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `sql_users_groups_users_id_group_id_4540dddc_uniq` (`users_id`,`group_id`),
KEY `sql_users_groups_group_id_d572a82e_fk_auth_group_id` (`group_id`),
CONSTRAINT `sql_users_groups_group_id_d572a82e_fk_auth_group_id` FOREIGN KEY (`group_id`) REFERENCES `auth_group` (`id`),
CONSTRAINT `sql_users_groups_users_id_d674bacf_fk_sql_users_id` FOREIGN KEY (`users_id`) REFERENCES `sql_users` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_users_groups 的数据：~0 rows (大约)
DELETE FROM `sql_users_groups`;
-- 导出 表 htmltooarchery.sql_users_resource_group 结构
DROP TABLE IF EXISTS `sql_users_resource_group`;
CREATE TABLE IF NOT EXISTS `sql_users_resource_group` (
`id` int NOT NULL AUTO_INCREMENT,
`users_id` int NOT NULL,
`resourcegroup_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `sql_users_resource_group_users_id_resourcegroup_id_304d8421_uniq` (`users_id`,`resourcegroup_id`),
KEY `sql_users_resource_g_resourcegroup_id_0738ff9d_fk_resource_` (`resourcegroup_id`),
CONSTRAINT `sql_users_resource_g_resourcegroup_id_0738ff9d_fk_resource_` FOREIGN KEY (`resourcegroup_id`) REFERENCES `resource_group` (`group_id`),
CONSTRAINT `sql_users_resource_group_users_id_fe4a5def_fk_sql_users_id` FOREIGN KEY (`users_id`) REFERENCES `sql_users` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_users_resource_group 的数据：~0 rows (大约)
DELETE FROM `sql_users_resource_group`;
-- 导出 表 htmltooarchery.sql_users_user_permissions 结构
DROP TABLE IF EXISTS `sql_users_user_permissions`;
CREATE TABLE IF NOT EXISTS `sql_users_user_permissions` (
`id` int NOT NULL AUTO_INCREMENT,
`users_id` int NOT NULL,
`permission_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `sql_users_user_permissions_users_id_permission_id_5fffb2bb_uniq` (`users_id`,`permission_id`),
KEY `sql_users_user_permi_permission_id_e990caab_fk_auth_perm` (`permission_id`),
CONSTRAINT `sql_users_user_permi_permission_id_e990caab_fk_auth_perm` FOREIGN KEY (`permission_id`) REFERENCES `auth_permission` (`id`),
CONSTRAINT `sql_users_user_permissions_users_id_efad14b0_fk_sql_users_id` FOREIGN KEY (`users_id`) REFERENCES `sql_users` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_users_user_permissions 的数据：~0 rows (大约)
DELETE FROM `sql_users_user_permissions`;
-- 导出 表 htmltooarchery.sql_workflow 结构
DROP TABLE IF EXISTS `sql_workflow`;
CREATE TABLE IF NOT EXISTS `sql_workflow` (
`id` int NOT NULL AUTO_INCREMENT,
`workflow_name` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`demand_url` varchar(500) COLLATE utf8mb4_general_ci NOT NULL,
`group_id` int NOT NULL,
`group_name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`db_name` varchar(64) COLLATE utf8mb4_general_ci NOT NULL,
`syntax_type` int NOT NULL,
`is_backup` tinyint(1) NOT NULL,
`engineer` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`engineer_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`status` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`audit_auth_groups` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`run_date_start` datetime(6) DEFAULT NULL,
`run_date_end` datetime(6) DEFAULT NULL,
`create_time` datetime(6) NOT NULL,
`finish_time` datetime(6) DEFAULT NULL,
`is_manual` int NOT NULL,
`instance_id` int NOT NULL,
PRIMARY KEY (`id`),
KEY `sql_workflow_instance_id_ad34809b_fk_sql_instance_id` (`instance_id`),
CONSTRAINT `sql_workflow_instance_id_ad34809b_fk_sql_instance_id` FOREIGN KEY (`instance_id`) REFERENCES `sql_instance` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_workflow 的数据：~0 rows (大约)
DELETE FROM `sql_workflow`;
-- 导出 表 htmltooarchery.sql_workflow_content 结构
DROP TABLE IF EXISTS `sql_workflow_content`;
CREATE TABLE IF NOT EXISTS `sql_workflow_content` (
`id` int NOT NULL AUTO_INCREMENT,
`sql_content` longtext COLLATE utf8mb4_general_ci NOT NULL,
`review_content` longtext COLLATE utf8mb4_general_ci NOT NULL,
`execute_result` longtext COLLATE utf8mb4_general_ci NOT NULL,
`workflow_id` int NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `workflow_id` (`workflow_id`),
CONSTRAINT `sql_workflow_content_workflow_id_3af79b62_fk_sql_workflow_id` FOREIGN KEY (`workflow_id`) REFERENCES `sql_workflow` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.sql_workflow_content 的数据：~0 rows (大约)
DELETE FROM `sql_workflow_content`;
-- 导出 表 htmltooarchery.ssh_tunnel 结构
DROP TABLE IF EXISTS `ssh_tunnel`;
CREATE TABLE IF NOT EXISTS `ssh_tunnel` (
`id` int NOT NULL AUTO_INCREMENT,
`tunnel_name` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`host` varchar(200) COLLATE utf8mb4_general_ci NOT NULL,
`port` int NOT NULL,
`user` varchar(200) COLLATE utf8mb4_general_ci DEFAULT NULL,
`password` varchar(300) COLLATE utf8mb4_general_ci DEFAULT NULL,
`pkey` longtext COLLATE utf8mb4_general_ci,
`pkey_path` varchar(100) COLLATE utf8mb4_general_ci DEFAULT NULL,
`pkey_password` varchar(300) COLLATE utf8mb4_general_ci DEFAULT NULL,
`create_time` datetime(6) NOT NULL,
`update_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `tunnel_name` (`tunnel_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.ssh_tunnel 的数据：~0 rows (大约)
DELETE FROM `ssh_tunnel`;
-- 导出 表 htmltooarchery.workflow_audit 结构
DROP TABLE IF EXISTS `workflow_audit`;
CREATE TABLE IF NOT EXISTS `workflow_audit` (
`audit_id` int NOT NULL AUTO_INCREMENT,
`group_id` int NOT NULL,
`group_name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`workflow_id` bigint NOT NULL,
`workflow_type` int NOT NULL,
`workflow_title` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`workflow_remark` varchar(140) COLLATE utf8mb4_general_ci NOT NULL,
`audit_auth_groups` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`current_audit` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`next_audit` varchar(20) COLLATE utf8mb4_general_ci NOT NULL,
`current_status` int NOT NULL,
`create_user` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`create_user_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`audit_id`),
UNIQUE KEY `workflow_audit_workflow_id_workflow_type_14044a22_uniq` (`workflow_id`,`workflow_type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.workflow_audit 的数据：~0 rows (大约)
DELETE FROM `workflow_audit`;
-- 导出 表 htmltooarchery.workflow_audit_detail 结构
DROP TABLE IF EXISTS `workflow_audit_detail`;
CREATE TABLE IF NOT EXISTS `workflow_audit_detail` (
`audit_detail_id` int NOT NULL AUTO_INCREMENT,
`audit_id` int NOT NULL,
`audit_user` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`audit_time` datetime(6) NOT NULL,
`audit_status` int NOT NULL,
`remark` varchar(1000) COLLATE utf8mb4_general_ci NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`audit_detail_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.workflow_audit_detail 的数据：~0 rows (大约)
DELETE FROM `workflow_audit_detail`;
-- 导出 表 htmltooarchery.workflow_audit_setting 结构
DROP TABLE IF EXISTS `workflow_audit_setting`;
CREATE TABLE IF NOT EXISTS `workflow_audit_setting` (
`audit_setting_id` int NOT NULL AUTO_INCREMENT,
`group_id` int NOT NULL,
`group_name` varchar(100) COLLATE utf8mb4_general_ci NOT NULL,
`workflow_type` int NOT NULL,
`audit_auth_groups` varchar(255) COLLATE utf8mb4_general_ci NOT NULL,
`create_time` datetime(6) NOT NULL,
`sys_time` datetime(6) NOT NULL,
PRIMARY KEY (`audit_setting_id`),
UNIQUE KEY `workflow_audit_setting_group_id_workflow_type_5884053a_uniq` (`group_id`,`workflow_type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.workflow_audit_setting 的数据：~0 rows (大约)
DELETE FROM `workflow_audit_setting`;
-- 导出 表 htmltooarchery.workflow_log 结构
DROP TABLE IF EXISTS `workflow_log`;
CREATE TABLE IF NOT EXISTS `workflow_log` (
`id` int NOT NULL AUTO_INCREMENT,
`audit_id` int NOT NULL,
`operation_type` smallint NOT NULL,
`operation_type_desc` varchar(10) COLLATE utf8mb4_general_ci NOT NULL,
`operation_info` varchar(1000) COLLATE utf8mb4_general_ci NOT NULL,
`operator` varchar(30) COLLATE utf8mb4_general_ci NOT NULL,
`operator_display` varchar(50) COLLATE utf8mb4_general_ci NOT NULL,
`operation_time` datetime(6) NOT NULL,
PRIMARY KEY (`id`),
KEY `workflow_log_audit_id_71ad84b7` (`audit_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
-- 正在导出表 htmltooarchery.workflow_log 的数据：~0 rows (大约)
DELETE FROM `workflow_log`;
/*!40103 SET TIME_ZONE=IFNULL(@OLD_TIME_ZONE, 'system') */;
/*!40101 SET SQL_MODE=IFNULL(@OLD_SQL_MODE, '') */;
/*!40014 SET FOREIGN_KEY_CHECKS=IFNULL(@OLD_FOREIGN_KEY_CHECKS, 1) */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40111 SET SQL_NOTES=IFNULL(@OLD_SQL_NOTES, 1) */;
追梦赤子心：domsn.com
签名：这个人很懒，什么也没有留下！
收藏的用户（0）
X
正在加载信息~
猜你喜欢：
- martinhelmich/xtrabackup
- dubbo-admin & zookeeper 部署
- APISIX 部署
- 自助Git+运维发布: Gogs+gopub
- inception+archer+goinception - SQL自动化运维系统
- 云监控告警系统: fluentd+filebeat+elasticsearch+logstash+kibana+prometheus+Grafana+报警
- 阿里巴巴 Sentinel + InfluxDB + Chronograf 实现监控大屏
- sentinel 部署 - 轻量级的流量控制、熔断降级
- MariaDB Galera Cluster基于galera cluster集群实现mysql数据库的高可用
- 阿里云/华为云系统盘扩容
最新回复 (0)