From 16d8b71e21dc7298b30f46bf264cd9b3589a6978 Mon Sep 17 00:00:00 2001
From: who's hu <hup_dev@outlook.com>
Date: Tue, 22 Aug 2023 17:25:19 +0800
Subject: [PATCH] update ruoyi-ui/src/permission.js. 由于重定向url存在 http://xxx.xx.xxx/{id}?param={a}&name={b} 的场景, 当未登录访问时, 通过改js封装登录后重定向参数, 会丢失?后的query params 如: 访问 http://localhost:1024/core/doc/doc?id=1683734914907807745&version=31 期望 http://localhost:1024/login?redirect=%2Fcore%2Fdoc%2Fdoc%3Fid%3D1683734914907807745%26version%3D31 实际通过 to.fullPath 封装后 获得 http://localhost:1024/login?redirect=%2Fcore%2Fdoc%2Fdoc%3Fid%3D1683734914907807745&version=31
---
sql/quartz.sql | 238 ++++++++++++++++++++++++++++++-----------------------------
1 files changed, 121 insertions(+), 117 deletions(-)
diff --git a/sql/quartz.sql b/sql/quartz.sql
index 52b6a09..5f99bfb 100644
--- a/sql/quartz.sql
+++ b/sql/quartz.sql
@@ -1,170 +1,174 @@
+DROP TABLE IF EXISTS QRTZ_FIRED_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_PAUSED_TRIGGER_GRPS;
+DROP TABLE IF EXISTS QRTZ_SCHEDULER_STATE;
+DROP TABLE IF EXISTS QRTZ_LOCKS;
+DROP TABLE IF EXISTS QRTZ_SIMPLE_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_SIMPROP_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_CRON_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_BLOB_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_TRIGGERS;
+DROP TABLE IF EXISTS QRTZ_JOB_DETAILS;
+DROP TABLE IF EXISTS QRTZ_CALENDARS;
+
-- ----------------------------
-- 1、存储每一个已配置的 jobDetail 的详细信息
-- ----------------------------
-drop table if exists QRTZ_JOB_DETAILS;
create table QRTZ_JOB_DETAILS (
- sched_name varchar(120) not null,
- job_name varchar(200) not null,
- job_group varchar(200) not null,
- description varchar(250) null,
- job_class_name varchar(250) not null,
- is_durable varchar(1) not null,
- is_nonconcurrent varchar(1) not null,
- is_update_data varchar(1) not null,
- requests_recovery varchar(1) not null,
- job_data blob null,
- primary key (sched_name,job_name,job_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ job_name varchar(200) not null comment '任务名称',
+ job_group varchar(200) not null comment '任务组名',
+ description varchar(250) null comment '相关介绍',
+ job_class_name varchar(250) not null comment '执行任务类名称',
+ is_durable varchar(1) not null comment '是否持久化',
+ is_nonconcurrent varchar(1) not null comment '是否并发',
+ is_update_data varchar(1) not null comment '是否更新数据',
+ requests_recovery varchar(1) not null comment '是否接受恢复执行',
+ job_data blob null comment '存放持久化job对象',
+ primary key (sched_name, job_name, job_group)
+) engine=innodb comment = '任务详细信息表';
-- ----------------------------
-- 2、 存储已配置的 Trigger 的信息
-- ----------------------------
-drop table if exists QRTZ_TRIGGERS;
create table QRTZ_TRIGGERS (
- sched_name varchar(120) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- job_name varchar(200) not null,
- job_group varchar(200) not null,
- description varchar(250) null,
- next_fire_time bigint(13) null,
- prev_fire_time bigint(13) null,
- priority integer null,
- trigger_state varchar(16) not null,
- trigger_type varchar(8) not null,
- start_time bigint(13) not null,
- end_time bigint(13) null,
- calendar_name varchar(200) null,
- misfire_instr smallint(2) null,
- job_data blob null,
- primary key (sched_name,trigger_name,trigger_group),
- foreign key (sched_name,job_name,job_group) references QRTZ_JOB_DETAILS(sched_name,job_name,job_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_name varchar(200) not null comment '触发器的名字',
+ trigger_group varchar(200) not null comment '触发器所属组的名字',
+ job_name varchar(200) not null comment 'qrtz_job_details表job_name的外键',
+ job_group varchar(200) not null comment 'qrtz_job_details表job_group的外键',
+ description varchar(250) null comment '相关介绍',
+ next_fire_time bigint(13) null comment '上一次触发时间（毫秒）',
+ prev_fire_time bigint(13) null comment '下一次触发时间（默认为-1表示不触发）',
+ priority integer null comment '优先级',
+ trigger_state varchar(16) not null comment '触发器状态',
+ trigger_type varchar(8) not null comment '触发器的类型',
+ start_time bigint(13) not null comment '开始时间',
+ end_time bigint(13) null comment '结束时间',
+ calendar_name varchar(200) null comment '日程表名称',
+ misfire_instr smallint(2) null comment '补偿执行的策略',
+ job_data blob null comment '存放持久化job对象',
+ primary key (sched_name, trigger_name, trigger_group),
+ foreign key (sched_name, job_name, job_group) references QRTZ_JOB_DETAILS(sched_name, job_name, job_group)
+) engine=innodb comment = '触发器详细信息表';
-- ----------------------------
-- 3、 存储简单的 Trigger，包括重复次数，间隔，以及已触发的次数
-- ----------------------------
-drop table if exists QRTZ_SIMPLE_TRIGGERS;
create table QRTZ_SIMPLE_TRIGGERS (
- sched_name varchar(120) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- repeat_count bigint(7) not null,
- repeat_interval bigint(12) not null,
- times_triggered bigint(10) not null,
- primary key (sched_name,trigger_name,trigger_group),
- foreign key (sched_name,trigger_name,trigger_group) references QRTZ_TRIGGERS(sched_name,trigger_name,trigger_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_name varchar(200) not null comment 'qrtz_triggers表trigger_name的外键',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ repeat_count bigint(7) not null comment '重复的次数统计',
+ repeat_interval bigint(12) not null comment '重复的间隔时间',
+ times_triggered bigint(10) not null comment '已经触发的次数',
+ primary key (sched_name, trigger_name, trigger_group),
+ foreign key (sched_name, trigger_name, trigger_group) references QRTZ_TRIGGERS(sched_name, trigger_name, trigger_group)
+) engine=innodb comment = '简单触发器的信息表';
-- ----------------------------
-- 4、 存储 Cron Trigger，包括 Cron 表达式和时区信息
-- ----------------------------
-drop table if exists QRTZ_CRON_TRIGGERS;
create table QRTZ_CRON_TRIGGERS (
- sched_name varchar(120) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- cron_expression varchar(200) not null,
- time_zone_id varchar(80),
- primary key (sched_name,trigger_name,trigger_group),
- foreign key (sched_name,trigger_name,trigger_group) references QRTZ_TRIGGERS(sched_name,trigger_name,trigger_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_name varchar(200) not null comment 'qrtz_triggers表trigger_name的外键',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ cron_expression varchar(200) not null comment 'cron表达式',
+ time_zone_id varchar(80) comment '时区',
+ primary key (sched_name, trigger_name, trigger_group),
+ foreign key (sched_name, trigger_name, trigger_group) references QRTZ_TRIGGERS(sched_name, trigger_name, trigger_group)
+) engine=innodb comment = 'Cron类型的触发器表';
-- ----------------------------
-- 5、 Trigger 作为 Blob 类型存储(用于 Quartz 用户用 JDBC 创建他们自己定制的 Trigger 类型，JobStore 并不知道如何存储实例的时候)
-- ----------------------------
-drop table if exists QRTZ_BLOB_TRIGGERS;
create table QRTZ_BLOB_TRIGGERS (
- sched_name varchar(120) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- blob_data blob null,
- primary key (sched_name,trigger_name,trigger_group),
- foreign key (sched_name,trigger_name,trigger_group) references QRTZ_TRIGGERS(sched_name,trigger_name,trigger_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_name varchar(200) not null comment 'qrtz_triggers表trigger_name的外键',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ blob_data blob null comment '存放持久化Trigger对象',
+ primary key (sched_name, trigger_name, trigger_group),
+ foreign key (sched_name, trigger_name, trigger_group) references QRTZ_TRIGGERS(sched_name, trigger_name, trigger_group)
+) engine=innodb comment = 'Blob类型的触发器表';
-- ----------------------------
-- 6、 以 Blob 类型存储存放日历信息， quartz可配置一个日历来指定一个时间范围
-- ----------------------------
-drop table if exists QRTZ_CALENDARS;
create table QRTZ_CALENDARS (
- sched_name varchar(120) not null,
- calendar_name varchar(200) not null,
- calendar blob not null,
- primary key (sched_name,calendar_name)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ calendar_name varchar(200) not null comment '日历名称',
+ calendar blob not null comment '存放持久化calendar对象',
+ primary key (sched_name, calendar_name)
+) engine=innodb comment = '日历信息表';
-- ----------------------------
-- 7、 存储已暂停的 Trigger 组的信息
-- ----------------------------
-drop table if exists QRTZ_PAUSED_TRIGGER_GRPS;
create table QRTZ_PAUSED_TRIGGER_GRPS (
- sched_name varchar(120) not null,
- trigger_group varchar(200) not null,
- primary key (sched_name,trigger_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ primary key (sched_name, trigger_group)
+) engine=innodb comment = '暂停的触发器表';
-- ----------------------------
-- 8、 存储与已触发的 Trigger 相关的状态信息，以及相联 Job 的执行信息
-- ----------------------------
-drop table if exists QRTZ_FIRED_TRIGGERS;
create table QRTZ_FIRED_TRIGGERS (
- sched_name varchar(120) not null,
- entry_id varchar(95) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- instance_name varchar(200) not null,
- fired_time bigint(13) not null,
- sched_time bigint(13) not null,
- priority integer not null,
- state varchar(16) not null,
- job_name varchar(200) null,
- job_group varchar(200) null,
- is_nonconcurrent varchar(1) null,
- requests_recovery varchar(1) null,
- primary key (sched_name,entry_id)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ entry_id varchar(95) not null comment '调度器实例id',
+ trigger_name varchar(200) not null comment 'qrtz_triggers表trigger_name的外键',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ instance_name varchar(200) not null comment '调度器实例名',
+ fired_time bigint(13) not null comment '触发的时间',
+ sched_time bigint(13) not null comment '定时器制定的时间',
+ priority integer not null comment '优先级',
+ state varchar(16) not null comment '状态',
+ job_name varchar(200) null comment '任务名称',
+ job_group varchar(200) null comment '任务组名',
+ is_nonconcurrent varchar(1) null comment '是否并发',
+ requests_recovery varchar(1) null comment '是否接受恢复执行',
+ primary key (sched_name, entry_id)
+) engine=innodb comment = '已触发的触发器表';
-- ----------------------------
-- 9、 存储少量的有关 Scheduler 的状态信息，假如是用于集群中，可以看到其他的 Scheduler 实例
-- ----------------------------
-drop table if exists QRTZ_SCHEDULER_STATE;
create table QRTZ_SCHEDULER_STATE (
- sched_name varchar(120) not null,
- instance_name varchar(200) not null,
- last_checkin_time bigint(13) not null,
- checkin_interval bigint(13) not null,
- primary key (sched_name,instance_name)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ instance_name varchar(200) not null comment '实例名称',
+ last_checkin_time bigint(13) not null comment '上次检查时间',
+ checkin_interval bigint(13) not null comment '检查间隔时间',
+ primary key (sched_name, instance_name)
+) engine=innodb comment = '调度器状态表';
-- ----------------------------
-- 10、 存储程序的悲观锁的信息(假如使用了悲观锁)
-- ----------------------------
-drop table if exists QRTZ_LOCKS;
create table QRTZ_LOCKS (
- sched_name varchar(120) not null,
- lock_name varchar(40) not null,
- primary key (sched_name,lock_name)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ lock_name varchar(40) not null comment '悲观锁名称',
+ primary key (sched_name, lock_name)
+) engine=innodb comment = '存储的悲观锁信息表';
-drop table if exists QRTZ_SIMPROP_TRIGGERS;
+-- ----------------------------
+-- 11、 Quartz集群实现同步机制的行锁表
+-- ----------------------------
create table QRTZ_SIMPROP_TRIGGERS (
- sched_name varchar(120) not null,
- trigger_name varchar(200) not null,
- trigger_group varchar(200) not null,
- str_prop_1 varchar(512) null,
- str_prop_2 varchar(512) null,
- str_prop_3 varchar(512) null,
- int_prop_1 int null,
- int_prop_2 int null,
- long_prop_1 bigint null,
- long_prop_2 bigint null,
- dec_prop_1 numeric(13,4) null,
- dec_prop_2 numeric(13,4) null,
- bool_prop_1 varchar(1) null,
- bool_prop_2 varchar(1) null,
- primary key (sched_name,trigger_name,trigger_group),
- foreign key (sched_name,trigger_name,trigger_group) references QRTZ_TRIGGERS(sched_name,trigger_name,trigger_group)
-) engine=innodb;
+ sched_name varchar(120) not null comment '调度名称',
+ trigger_name varchar(200) not null comment 'qrtz_triggers表trigger_name的外键',
+ trigger_group varchar(200) not null comment 'qrtz_triggers表trigger_group的外键',
+ str_prop_1 varchar(512) null comment 'String类型的trigger的第一个参数',
+ str_prop_2 varchar(512) null comment 'String类型的trigger的第二个参数',
+ str_prop_3 varchar(512) null comment 'String类型的trigger的第三个参数',
+ int_prop_1 int null comment 'int类型的trigger的第一个参数',
+ int_prop_2 int null comment 'int类型的trigger的第二个参数',
+ long_prop_1 bigint null comment 'long类型的trigger的第一个参数',
+ long_prop_2 bigint null comment 'long类型的trigger的第二个参数',
+ dec_prop_1 numeric(13,4) null comment 'decimal类型的trigger的第一个参数',
+ dec_prop_2 numeric(13,4) null comment 'decimal类型的trigger的第二个参数',
+ bool_prop_1 varchar(1) null comment 'Boolean类型的trigger的第一个参数',
+ bool_prop_2 varchar(1) null comment 'Boolean类型的trigger的第二个参数',
+ primary key (sched_name, trigger_name, trigger_group),
+ foreign key (sched_name, trigger_name, trigger_group) references QRTZ_TRIGGERS(sched_name, trigger_name, trigger_group)
+) engine=innodb comment = '同步机制的行锁表';
commit;
\ No newline at end of file
--
Gitblit v1.9.2