更新密码找回uniapp
This commit is contained in:
1 parent
7f9a66da0f
commit
3fdda89833
1304 files changed
+3503
-26132
No files matched your search
@@ -1,30 +1,3 @@
|
||||
# ============================================================
|
||||
# 宝塔站点 api.yunzer.cn 的 nginx 配置(留档副本)
|
||||
# 文件位置(服务器):/www/server/panel/vhost/nginx/api.yunzer.cn.conf
|
||||
# 面板入口:宝塔 → 网站 → api.yunzer.cn → 设置 → 配置文件
|
||||
#
|
||||
# 【2026-10-31 新增】根路径域名校验文件的 http 放行
|
||||
# 微信公众平台 / 小程序配置「业务域名」时,校验服务是走 **http**
|
||||
# 去抓取根目录下的校验文件(如 /1XXl8fPHr9.txt)。
|
||||
# 原配置把 http 一律 301 到 https,微信拿到重定向就判
|
||||
# 「校验文件验证失败,请确认已在域名根目录正确放置校验文件」。
|
||||
# 下面 HTTP_TO_HTTPS 块里新增的 if 例外,就是让根路径下的 .txt
|
||||
# 校验文件在 http 下直接返回文件内容(不跳转)。
|
||||
# 用通配而不是写死文件名:微信每次重新下载校验文件都会生成新随机名。
|
||||
#
|
||||
# 【注意】不要设 verify_hosts
|
||||
# 本文件里 proxy_set_header Host 10.31.100.2; 把 Host 头改成了 IP,
|
||||
# Go 侧看不到 api.yunzer.cn 这个域名。verify_hosts 必须留空
|
||||
# (留空 = 所有走本服务的域名都放行)。
|
||||
#
|
||||
# 【注意】location ^~ / 会让后面的正则 location 失效
|
||||
# ^~ 匹配后 nginx 不再检查正则 location,所以下面两条
|
||||
# 「禁止访问的敏感文件 / 敏感目录」的 location ~* 规则在本站点实际不生效。
|
||||
# 当前无泄露风险(Go 不提供工作目录文件,未知路径一律 404),但要知道这层保护是空的。
|
||||
#
|
||||
# 【注意】proxy_cache_path 定义了缓存区但当前未启用 proxy_cache
|
||||
# 以后若启用全局缓存,301 会被缓存住,微信可能拿到缓存的旧响应,届时需清缓存。
|
||||
# ============================================================
|
||||
|
||||
proxy_cache_path /www/wwwroot/api.yunzer.cn/proxy_cache_dir levels=1:2 keys_zone=api_yunzer_cn_cache:20m inactive=1d max_size=5g;
|
||||
server {
|
||||
@@ -36,17 +9,12 @@ server {
|
||||
index index.php index.html index.htm default.php default.htm default.html;
|
||||
root /www/wwwroot/api.yunzer.cn;
|
||||
include /www/server/panel/vhost/nginx/extension/api.yunzer.cn/*.conf;
|
||||
#CERT-APPLY-CHECK--START
|
||||
|
||||
# 用于SSL证书申请时的文件验证相关配置 -- 请勿删除
|
||||
include /www/server/panel/vhost/nginx/well-known/api.yunzer.cn.conf;
|
||||
#CERT-APPLY-CHECK--END
|
||||
|
||||
#SSL-START SSL相关配置,请勿删除或修改下一行带注释的404规则
|
||||
|
||||
#error_page 404/404.html;
|
||||
|
||||
#HTTP_TO_HTTPS_START
|
||||
set $isRedcert 1;
|
||||
if ($server_port != 443) {
|
||||
set $isRedcert 2;
|
||||
@@ -54,15 +22,12 @@ server {
|
||||
if ( $uri ~ /\.well-known/ ) {
|
||||
set $isRedcert 1;
|
||||
}
|
||||
# 域名校验文件(微信/搜索引擎/第三方平台)必须能用 http 直接访问,不能 301 跳 https。
|
||||
# 用 [.] 代替 \. ,避免 nginx 配置解析里反斜杠转义的歧义。
|
||||
if ( $uri ~ ^/[A-Za-z0-9._-]+[.]txt$ ) {
|
||||
set $isRedcert 1;
|
||||
}
|
||||
if ($isRedcert != 1) {
|
||||
rewrite ^(/.*)$ https://$host$1 permanent;
|
||||
}
|
||||
#HTTP_TO_HTTPS_END
|
||||
ssl_certificate /www/server/panel/vhost/cert/api.yunzer.cn/fullchain.pem;
|
||||
ssl_certificate_key /www/server/panel/vhost/cert/api.yunzer.cn/privkey.pem;
|
||||
ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
|
||||
@@ -75,49 +40,16 @@ server {
|
||||
error_page 497 https://$host$request_uri;
|
||||
#SSL-END
|
||||
|
||||
#REDIRECT START
|
||||
|
||||
#REDIRECT END
|
||||
|
||||
#ERROR-PAGE-START 错误页配置,可以注释、删除或修改
|
||||
|
||||
#error_page 404 /404.html;
|
||||
|
||||
#error_page 502 /502.html;
|
||||
|
||||
#ERROR-PAGE-END
|
||||
|
||||
#PHP-INFO-START PHP引用配置,可以注释或修改
|
||||
include enable-php-00.conf;
|
||||
#PHP-INFO-END
|
||||
|
||||
#IP-RESTRICT-START 限制访问ip的配置,IP黑白名单
|
||||
|
||||
#IP-RESTRICT-END
|
||||
|
||||
#BASICAUTH START
|
||||
|
||||
#BASICAUTH END
|
||||
|
||||
#SUB_FILTER START
|
||||
|
||||
#SUB_FILTER END
|
||||
|
||||
#GZIP START
|
||||
|
||||
#GZIP END
|
||||
|
||||
#GLOBAL-CACHE START
|
||||
|
||||
#GLOBAL-CACHE END
|
||||
|
||||
#WEBSOCKET-SUPPORT START
|
||||
proxy_http_version 1.1;
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection $connection_upgrade;
|
||||
#WEBSOCKET-SUPPORT END
|
||||
|
||||
#PROXY-CONF-START
|
||||
location ^~ / {
|
||||
proxy_pass http://10.31.100.2:9000;
|
||||
proxy_set_header Host 10.31.100.2;
|
||||
@@ -128,52 +60,32 @@ server {
|
||||
proxy_set_header X-Forwarded-Host $host;
|
||||
proxy_set_header X-Forwarded-Port $server_port;
|
||||
proxy_set_header REMOTE-HOST $remote_addr;
|
||||
# 连接超时(建立连接的时间)
|
||||
proxy_connect_timeout 3600s;
|
||||
# 发送超时(发送请求到后端的时间)
|
||||
proxy_send_timeout 3600s;
|
||||
# 读取超时(等待后端响应的时间)
|
||||
proxy_read_timeout 3600s;
|
||||
# 支持websocket链接
|
||||
proxy_http_version 1.1;
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection $connection_upgrade;
|
||||
# 客户端请求体大小限制(0 表示不限制)
|
||||
client_max_body_size 0;
|
||||
# 客户端请求体超时(客户端发送请求体的时间)
|
||||
client_body_timeout 3600s;
|
||||
# 客户端请求体缓冲区大小
|
||||
client_body_buffer_size 128k;
|
||||
# 禁用请求体缓冲(直接流式传输到后端,不先缓存到磁盘)
|
||||
proxy_request_buffering off;
|
||||
# 禁用响应缓冲(直接流式传输到客户端)
|
||||
proxy_buffering off;
|
||||
}
|
||||
#PROXY-CONF-END
|
||||
|
||||
#SERVER-BLOCK START
|
||||
|
||||
#SERVER-BLOCK END
|
||||
|
||||
# 禁止访问的敏感文件
|
||||
location ~* (\.user.ini|\.htaccess|\.htpasswd|\.env.*|\.project|\.bashrc|\.bash_profile|\.bash_logout|\.DS_Store|\.gitignore|\.gitattributes|LICENSE|README\.md|CLAUDE\.md|CHANGELOG\.md|CHANGELOG|CONTRIBUTING\.md|TODO\.md|FAQ\.md|composer\.json|composer\.lock|package(-lock)?\.json|yarn\.lock|pnpm-lock\.yaml|\.\w+~|\.swp|\.swo|\.bak(up)?|\.old|\.tmp|\.temp|\.log|\.sql(\.gz)?|docker-compose\.yml|docker\.env|Dockerfile|\.csproj|\.sln|Cargo\.toml|Cargo\.lock|go\.mod|go\.sum|phpunit\.xml|phpunit\.xml|pom\.xml|build\.gradl|pyproject\.toml|requirements\.txt|application(-\w+)?\.(ya?ml|properties))$ {
|
||||
return 404;
|
||||
}
|
||||
# 禁止访问的敏感目录
|
||||
location ~* /(\.git|\.svn|\.bzr|\.vscode|\.claude|\.idea|\.ssh|\.github|\.npm|\.yarn|\.pnpm|\.cache|\.husky|\.turbo|\.next|\.nuxt|node_modules|runtime)/ {
|
||||
return 404;
|
||||
}
|
||||
#一键申请SSL证书验证目录相关设置
|
||||
location /.well-known {
|
||||
allow all;
|
||||
}
|
||||
#禁止在证书验证目录放入敏感文件
|
||||
if ( $uri ~ "^/\.well-known/.*\.(php|jsp|py|js|css|lua|ts|go|zip|tar\.gz|rar|7z|sql|bak)$" ) {
|
||||
return 403;
|
||||
}
|
||||
#LOG START
|
||||
access_log /www/wwwlogs/api.yunzer.cn.log;
|
||||
error_log /www/wwwlogs/api.yunzer.cn.error.log;
|
||||
#LOG END
|
||||
|
||||
}
|
||||
@@ -1,30 +1,4 @@
|
||||
-- =============================================================
|
||||
-- 模块 / 菜单「展示端(platforms)」
|
||||
--
|
||||
-- 需求:后台管理模块层面需要能判断一个模块(及其菜单)
|
||||
-- 是 Web 端显示、小程序显示,还是两端都显示。
|
||||
--
|
||||
-- 与已有的 views 字段是两个独立维度,不要混淆:
|
||||
-- views —— [1]平台端 / [2]租户端(决定出现在哪个后台)
|
||||
-- platforms —— ["web"] / ["app"] / ["web","app"](决定 Web 还是移动端可见)
|
||||
--
|
||||
-- 取值约定:
|
||||
-- ["web"] 仅 Web 端(租户管理后台)可见
|
||||
-- ["app"] 仅移动端(uniapp APP / 微信小程序)可见
|
||||
-- ["web","app"] 两端都可见
|
||||
-- '' 或 NULL 全端可见(默认,保证历史数据行为不变)
|
||||
--
|
||||
-- 继承规则:
|
||||
-- 菜单自身配置了 platforms → 以自身为准
|
||||
-- 菜单未配置 → 继承所属模块的 platforms(按 path 前缀归属)
|
||||
-- 两者都未配置 → 全端可见
|
||||
--
|
||||
-- 本脚本可重复执行:MySQL 不支持 ADD COLUMN IF NOT EXISTS,
|
||||
-- 故先用 information_schema 判断,再由动态 SQL 决定加不加列。
|
||||
-- 若已存在则只更新注释,不会报 1060 Duplicate column name。
|
||||
-- =============================================================
|
||||
|
||||
-- ---------- yz_system_modules ----------
|
||||
SET @db := DATABASE();
|
||||
SET @tbl := 'yz_system_modules';
|
||||
SET @col := 'platforms';
|
||||
@@ -40,7 +14,6 @@ SET @sql := IF(@exists = 0,
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- ---------- yz_system_menu ----------
|
||||
SET @tbl := 'yz_system_menu';
|
||||
SET @exists := (
|
||||
SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
@@ -54,36 +27,8 @@ SET @sql := IF(@exists = 0,
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- ---------- 校验 ----------
|
||||
SELECT TABLE_NAME, COLUMN_NAME, COLUMN_TYPE, IS_NULLABLE, COLUMN_COMMENT
|
||||
FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND COLUMN_NAME = 'platforms'
|
||||
AND TABLE_NAME IN ('yz_system_modules', 'yz_system_menu');
|
||||
|
||||
-- =============================================================
|
||||
-- 使用示例(按需执行)
|
||||
-- 注意:MySQL 5.7+ 可直接用 JSON_ARRAY('web') 生成 '["web"]',
|
||||
-- 比手写转义双引号更省事。
|
||||
-- =============================================================
|
||||
|
||||
-- 例1:把「客户关系管理」设为仅 Web 端可见(移动端不显示该子系统卡片)
|
||||
-- UPDATE yz_system_modules SET platforms = JSON_ARRAY('web') WHERE code = 'crm';
|
||||
|
||||
-- 例2:把「便捷工具」设为仅移动端可见(Web 端后台不再展示)
|
||||
-- UPDATE yz_system_modules SET platforms = JSON_ARRAY('app') WHERE code = 'bianjiegongju';
|
||||
|
||||
-- 例3:某功能两端都要
|
||||
-- UPDATE yz_system_modules SET platforms = JSON_ARRAY('web','app') WHERE code = 'cms';
|
||||
|
||||
-- 例4:某个具体功能只在小程序上用(如扫码打卡),单独给菜单配置
|
||||
-- UPDATE yz_system_menu SET platforms = JSON_ARRAY('app') WHERE path = '/tools/notebook';
|
||||
|
||||
-- 例5:恢复全端可见(清空即可,NULL 与 '' 都表示全端)
|
||||
-- UPDATE yz_system_modules SET platforms = NULL WHERE code = 'crm';
|
||||
-- UPDATE yz_system_modules SET platforms = NULL; -- 全部恢复
|
||||
|
||||
-- =============================================================
|
||||
-- 回滚
|
||||
-- =============================================================
|
||||
-- ALTER TABLE yz_system_modules DROP COLUMN platforms;
|
||||
-- ALTER TABLE yz_system_menu DROP COLUMN platforms;
|
||||
@@ -1,29 +1,10 @@
|
||||
-- =============================================================
|
||||
-- 角色「平台下发 + 租户只读」显式锁定 - 增量迁移
|
||||
--
|
||||
-- 场景:平台端可建 cid=2 且 tenant_id=0 的全局角色下发到租户后台。
|
||||
-- 此前"租户不可改/不可删"的判定绑死在 tenant_id==0 上,
|
||||
-- 一是无法表达"落到具体租户头上但仍只读",
|
||||
-- 二是后端看 tenant_id、前端看 is_custom,两处口径不一致会漂移。
|
||||
-- 本迁移把锁定语义收敛为独立列 is_locked。
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) 加 is_locked / source_role_id 两列
|
||||
-- 2) 回填:现存全局租户角色(cid=2 且 tenant_id=0)标记为锁定,
|
||||
-- 保证代码改用 is_locked 判定后,这两个角色不会突然变得可被租户改写。
|
||||
--
|
||||
-- 注意:MySQL 不支持 ADD COLUMN IF NOT EXISTS,本脚本重复执行会在第 1 步
|
||||
-- 报 Duplicate column name 并停止,属预期,不会破坏已回填的数据。
|
||||
-- =============================================================
|
||||
|
||||
-- 1. 角色表补锁定列
|
||||
ALTER TABLE `yz_system_admin_role`
|
||||
ADD COLUMN `is_locked` TINYINT UNSIGNED NOT NULL DEFAULT 0
|
||||
COMMENT '1=平台下发,租户端只读(不可改名/改权限/删除)' AFTER `is_custom`,
|
||||
ADD COLUMN `source_role_id` BIGINT UNSIGNED NOT NULL DEFAULT 0
|
||||
COMMENT '来源角色ID(平台下发时记录,0=非下发)' AFTER `is_locked`;
|
||||
|
||||
-- 2. 回填存量全局租户角色
|
||||
UPDATE `yz_system_admin_role`
|
||||
SET `is_locked` = 1
|
||||
WHERE `cid` = 2
|
||||
|
||||
@@ -1,15 +1,4 @@
|
||||
-- =============================================================
|
||||
-- 审批流双层绑定重构 v2 - 增量迁移
|
||||
--
|
||||
-- 场景:上一版 create_approval_binding.sql 已建表但含 condition_expr/priority
|
||||
-- 本次将绑定层简化为纯关联,流程表加 apply_dept_ids 部门作用域。
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) DROP + 重建绑定表(结构变简,无法原地迁移)
|
||||
-- 2) 后端流程表补 apply_dept_ids
|
||||
-- =============================================================
|
||||
|
||||
-- 1. 绑定表:先删后建(如已有绑定数据请手工备份后再执行)
|
||||
DROP TABLE IF EXISTS `yz_approval_binding`;
|
||||
|
||||
CREATE TABLE `yz_approval_binding` (
|
||||
@@ -28,7 +17,6 @@ CREATE TABLE `yz_approval_binding` (
|
||||
KEY `idx_flow` (`flow_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='审批流功能绑定(biz_type↔flow 多对多)';
|
||||
|
||||
-- 2. 后端流程表:补部门作用域列
|
||||
ALTER TABLE `yz_backend_approval_flow`
|
||||
ADD COLUMN `apply_dept_ids` VARCHAR(500) NOT NULL DEFAULT ''
|
||||
COMMENT '适用部门ID列表 CSV,空=全公司通用' AFTER `flow_code`;
|
||||
@@ -1,33 +1,23 @@
|
||||
-- =============================================================
|
||||
-- 审批流图编辑器 - 增量迁移(对已存在的旧表补列)
|
||||
-- MySQL 兼容写法:如列已存在会报错,跳过该条即可
|
||||
-- 如果表本身不存在,请先执行 create_approval_flow.sql
|
||||
-- =============================================================
|
||||
|
||||
-- 1. 租户侧流程表:补 flow_code
|
||||
ALTER TABLE `yz_backend_approval_flow`
|
||||
ADD COLUMN `flow_code` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '审批流编号(自动生成 FL%06d)' AFTER `biz_type`;
|
||||
|
||||
ALTER TABLE `yz_backend_approval_flow`
|
||||
ADD INDEX `idx_tid_code` (`tid`, `flow_code`);
|
||||
|
||||
-- 2. 租户侧节点表:补 pos_x / pos_y
|
||||
ALTER TABLE `yz_backend_approval_node`
|
||||
ADD COLUMN `pos_x` INT NOT NULL DEFAULT 0 COMMENT '画布X坐标' AFTER `sort`,
|
||||
ADD COLUMN `pos_y` INT NOT NULL DEFAULT 0 COMMENT '画布Y坐标' AFTER `pos_x`;
|
||||
|
||||
-- 3. 平台侧流程表:补 flow_code
|
||||
ALTER TABLE `yz_platform_approval_flow`
|
||||
ADD COLUMN `flow_code` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '审批流编号(自动生成 FL%06d)' AFTER `biz_type`;
|
||||
|
||||
ALTER TABLE `yz_platform_approval_flow`
|
||||
ADD INDEX `idx_code` (`flow_code`);
|
||||
|
||||
-- 4. 平台侧节点表:补 pos_x / pos_y
|
||||
ALTER TABLE `yz_platform_approval_node`
|
||||
ADD COLUMN `pos_x` INT NOT NULL DEFAULT 0 COMMENT '画布X坐标' AFTER `sort`,
|
||||
ADD COLUMN `pos_y` INT NOT NULL DEFAULT 0 COMMENT '画布Y坐标' AFTER `pos_x`;
|
||||
|
||||
-- 5. 实例表:补 form_data(条件求值用表单快照 JSON)
|
||||
ALTER TABLE `yz_approval_instance`
|
||||
ADD COLUMN `form_data` TEXT NULL COMMENT '发起表单数据快照(JSON)' AFTER `submit_dept_id`;
|
||||
@@ -1,10 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 统一身份层增加「全局登录账号」列(账号注册方式)
|
||||
-- 手机号注册:mobile 即账号;账号注册:自定义账号名存本列,
|
||||
-- 登录查找链 FindIdentityByAccount 按账号 → 手机号 → 邮箱匹配。
|
||||
-- 唯一索引允许多个 NULL(手机号注册的身份不填账号列)。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < alter_auth_identity_account.sql
|
||||
-- ============================================================
|
||||
|
||||
ALTER TABLE yz_auth_identity
|
||||
ADD COLUMN account varchar(64) NULL DEFAULT NULL COMMENT '全局登录账号(账号注册;NULL 表示手机号注册身份)' AFTER union_id;
|
||||
@@ -12,5 +5,4 @@ ALTER TABLE yz_auth_identity
|
||||
ALTER TABLE yz_auth_identity
|
||||
ADD UNIQUE KEY uk_auth_identity_account (account);
|
||||
|
||||
-- 结果校验
|
||||
SHOW COLUMNS FROM yz_auth_identity LIKE 'account';
|
||||
@@ -1,9 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 小程序「挂靠企业」申请表补列
|
||||
-- 前置:yz_auth_tenant_apply 已由 create_auth_tenant_apply.sql 创建。
|
||||
-- 幂等说明:MySQL 5.7/8.0 不支持 ADD COLUMN IF NOT EXISTS,
|
||||
-- 重复执行会报 Duplicate column,可忽略(先 SELECT 确认)。
|
||||
-- ============================================================
|
||||
|
||||
ALTER TABLE `yz_auth_tenant_apply`
|
||||
ADD COLUMN `applicant_name` varchar(64) NOT NULL DEFAULT '' COMMENT '申请人姓名(挂靠表单填写)' AFTER `identity_id`,
|
||||
|
||||
@@ -1,16 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 项目上游主体支持从「供应商库」选择(CRM 项目管理)
|
||||
--
|
||||
-- 背景:上游主体(customer_id / customer_name)原本固定取客户库;
|
||||
-- 同一家单位在系统里可能只以供应商身份建档,因此上游也允许从供应商库选择。
|
||||
-- 新增列 yz_backend_crm_project.customer_ref_type:
|
||||
-- 1 = 客户库(默认,历史数据同此)
|
||||
-- 2 = 供应商库
|
||||
--
|
||||
-- 幂等:MySQL 的 ADD COLUMN 不支持 IF NOT EXISTS,这里先用 information_schema
|
||||
-- 判断列是否存在,缺失才执行 ALTER,可重复执行。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < alter_crm_project_customer_ref_type.sql
|
||||
-- =============================================================
|
||||
|
||||
SET @has_col := (SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
@@ -25,7 +12,6 @@ PREPARE stmt FROM @sql;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 结果校验:应返回一行 customer_ref_type
|
||||
SELECT COLUMN_NAME, COLUMN_TYPE, COLUMN_DEFAULT, COLUMN_COMMENT
|
||||
FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
|
||||
@@ -0,0 +1,48 @@
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
SET @sql := IF(
|
||||
(SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_oa_attendance' AND COLUMN_NAME = 'fix_status') = 0,
|
||||
'ALTER TABLE `yz_backend_oa_attendance` ADD COLUMN `fix_status` TINYINT NOT NULL DEFAULT 0 COMMENT ''补卡状态 0未申请 1审批中 2已通过 3已驳回 4已撤回'' AFTER `source`',
|
||||
'SELECT 1'
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
SET @sql := IF(
|
||||
(SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_oa_attendance' AND COLUMN_NAME = 'fix_type') = 0,
|
||||
'ALTER TABLE `yz_backend_oa_attendance` ADD COLUMN `fix_type` TINYINT NOT NULL DEFAULT 0 COMMENT ''补卡类型 1签到 2签退'' AFTER `fix_status`',
|
||||
'SELECT 1'
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
SET @sql := IF(
|
||||
(SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_oa_attendance' AND COLUMN_NAME = 'fix_instance_id') = 0,
|
||||
'ALTER TABLE `yz_backend_oa_attendance` ADD COLUMN `fix_instance_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT ''补卡审批实例ID'' AFTER `fix_type`',
|
||||
'SELECT 1'
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
SET @sql := IF(
|
||||
(SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_oa_attendance' AND COLUMN_NAME = 'fix_time') = 0,
|
||||
'ALTER TABLE `yz_backend_oa_attendance` ADD COLUMN `fix_time` VARCHAR(8) NOT NULL DEFAULT '''' COMMENT ''补录打卡时间 HH:mm'' AFTER `fix_instance_id`',
|
||||
'SELECT 1'
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
SET @sql := IF(
|
||||
(SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_oa_attendance' AND COLUMN_NAME = 'fix_reason') = 0,
|
||||
'ALTER TABLE `yz_backend_oa_attendance` ADD COLUMN `fix_reason` VARCHAR(255) NOT NULL DEFAULT '''' COMMENT ''补卡原因'' AFTER `fix_time`',
|
||||
'SELECT 1'
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
SELECT COLUMN_NAME, COLUMN_TYPE, COLUMN_COMMENT
|
||||
FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
AND TABLE_NAME = 'yz_backend_oa_attendance'
|
||||
AND COLUMN_NAME IN ('fix_status', 'fix_type', 'fix_instance_id', 'fix_time', 'fix_reason');
|
||||
@@ -1,28 +1,10 @@
|
||||
-- =============================================================
|
||||
-- OA工作日报:删除改为软删除(已建表环境执行)
|
||||
--
|
||||
-- 背景:原设计为物理删除(日报被删时同步删除评论),现改为软删除。
|
||||
-- 日报:is_deleted=0 未删除;删除时写入记录 ID 作为删除批次标记。
|
||||
-- 评论:is_deleted=0 未删除;删除时置 1。
|
||||
--
|
||||
-- 为什么唯一键要加 is_deleted:
|
||||
-- 原唯一键 (tid, user_id, report_date) 会让「删除后同一天重新填写」与
|
||||
-- 历史软删记录冲突。把 is_deleted 加入唯一键后,删除时写入记录 ID
|
||||
-- (每条记录 ID 唯一),同一天可反复「填写→删除→重新填写」。
|
||||
--
|
||||
-- 适用:已执行过 create_oa_dailyreport.sql 的环境;
|
||||
-- 新库直接执行 create_oa_dailyreport.sql 即为软删除结构,无需本脚本。
|
||||
-- 幂等:重复执行安全。
|
||||
-- =============================================================
|
||||
|
||||
USE `go-platform`;
|
||||
|
||||
-- 1) is_deleted 扩为 BIGINT UNSIGNED,用于存放删除批次(记录 ID)。MODIFY 幂等。
|
||||
ALTER TABLE `yz_backend_oa_daily_report`
|
||||
MODIFY COLUMN `is_deleted` BIGINT UNSIGNED NOT NULL DEFAULT 0
|
||||
COMMENT '软删除标记:0=未删除;删除时写入记录ID(避免唯一键冲突)';
|
||||
|
||||
-- 2) 唯一键加入 is_deleted(先判断当前索引列,避免重复执行报 1091)
|
||||
SET @idx_cols := (
|
||||
SELECT GROUP_CONCAT(`COLUMN_NAME` ORDER BY `SEQ_IN_INDEX`)
|
||||
FROM `information_schema`.`STATISTICS`
|
||||
@@ -39,6 +21,5 @@ PREPARE stmt FROM @ddl;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 3) 核对结果
|
||||
SHOW INDEX FROM `yz_backend_oa_daily_report` WHERE `Key_name` = 'uk_tid_user_date';
|
||||
SHOW FULL COLUMNS FROM `yz_backend_oa_daily_report` WHERE `Field` = 'is_deleted';
|
||||
@@ -1,21 +1,6 @@
|
||||
-- =============================================================
|
||||
-- OA 报销:费用明细支持「发票挂靠」(已建表环境执行)
|
||||
--
|
||||
-- 背景:一张发票(例如 200 元油票/邮费票)常常需要分多次报销才能报满。
|
||||
-- 现在每条费用明细可以挂靠一张「仍有余额的发票」,并记录本次使用金额。
|
||||
--
|
||||
-- 设计:不新建发票表,发票本体仍是明细行 receipt_file_ids 指向的附件。
|
||||
-- 票面金额取 receipt_amounts(OCR 识别或人工填写),余额由后端实时聚合:
|
||||
-- 余额 = 票面金额 - 上传该票的明细占用 - 其它明细挂靠占用
|
||||
-- 明细被删除后占用自动释放,无需额外回滚,也不存在余额字段不一致问题。
|
||||
--
|
||||
-- 适用:已有 yz_backend_reimbursement_items 的环境。
|
||||
-- 幂等:重复执行安全(information_schema 判断列是否存在)。
|
||||
-- =============================================================
|
||||
|
||||
USE `go-platform`;
|
||||
|
||||
-- 1) 挂靠的发票文件 ID(0 = 未挂靠)
|
||||
SET @ddl := (
|
||||
SELECT IF(
|
||||
EXISTS (
|
||||
@@ -32,7 +17,6 @@ PREPARE stmt FROM @ddl;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 2) 本条明细本次使用的发票金额
|
||||
SET @ddl := (
|
||||
SELECT IF(
|
||||
EXISTS (
|
||||
@@ -49,7 +33,6 @@ PREPARE stmt FROM @ddl;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 3) 辅助索引:按挂靠发票快速聚合(重复执行前先判断)
|
||||
SET @ddl := (
|
||||
SELECT IF(
|
||||
EXISTS (
|
||||
@@ -66,6 +49,5 @@ PREPARE stmt FROM @ddl;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 4) 核对结果
|
||||
SHOW FULL COLUMNS FROM `yz_backend_reimbursement_items`
|
||||
WHERE `Field` IN ('invoice_file_id', 'invoice_use_amount');
|
||||
@@ -1,31 +1,4 @@
|
||||
-- ============================================================
|
||||
-- OA 工作排班:排班方案支持「平台模板 + 周期规则」
|
||||
--
|
||||
-- 适用:已执行过 create_oa_scheduling.sql 的环境(表已存在)。
|
||||
-- 执行:在业务库(go-platform)下整段执行即可。
|
||||
--
|
||||
-- 幂等:逐列判断 information_schema,只添加缺失的列;
|
||||
-- 9 列全部存在时自动跳过一次无害查询,不会报 1060。
|
||||
--
|
||||
-- 字段说明:
|
||||
-- template_id / template_code / template_name
|
||||
-- 方案来源模板的快照。租户调用模板后,模板规则会复制进本方案,
|
||||
-- 之后模板调整或停用都不影响已保存方案(platform 模板只读,租户可改自己的)。
|
||||
-- align_mode
|
||||
-- 0 = 未使用模板(沿用 weekdays + shift_id 的按星期排班)
|
||||
-- 1 = 按自然周(双休 / 单休 / 大小周)
|
||||
-- 2 = 从 start_date 起滚动(三班倒 / 做一休一)
|
||||
-- 3 = 按自然月(月休)
|
||||
-- cycle_days 周期天数(align_mode=1/2 时等于 pattern 长度)
|
||||
-- week_offset 大小周起始周偏移:0=开始日期所在周为周期第 1 周,1=第 2 周
|
||||
-- month_rest_days 月休:每月休息天数
|
||||
-- month_rest_weekday 月休固定休息周几(1-7),0 表示不固定
|
||||
-- pattern 周期规则 JSON 快照,元素形如
|
||||
-- {"day_index":0,"day_type":1,"shift_id":12,"shift_name":"白班",
|
||||
-- "short_name":"白","color":"#409EFF","work_start":"09:00","work_end":"18:00"}
|
||||
-- ============================================================
|
||||
|
||||
-- 执行前自查:existing_cols = 9 表示字段已齐全,执行到下面会自动跳过
|
||||
SELECT COUNT(*) AS existing_cols
|
||||
FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
@@ -53,16 +26,13 @@ SET @sql := CONCAT('ALTER TABLE `yz_backend_oa_schedule_plan` ',
|
||||
'ADD COLUMN `pattern` TEXT NULL COMMENT ''周期规则JSON快照'', ', '')
|
||||
);
|
||||
|
||||
-- 去掉结尾多余的 ", "(两个字符),否则 ALTER 语句会因尾逗号报 1064
|
||||
SET @sql := IF(RIGHT(@sql, 2) = ', ', LEFT(@sql, CHAR_LENGTH(@sql) - 2), @sql);
|
||||
-- 没有任何缺失列时,@sql 只剩表名,替换为一条无害语句
|
||||
SET @sql := IF(RIGHT(@sql, 6) = 'TABLE ', 'SELECT 1 AS skipped_all_columns_exist', @sql);
|
||||
|
||||
PREPARE stmt FROM @sql;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- 核对结果:应返回 9 行
|
||||
SELECT COLUMN_NAME, COLUMN_TYPE, COLUMN_DEFAULT, COLUMN_COMMENT
|
||||
FROM information_schema.COLUMNS
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
|
||||
@@ -1,4 +1,2 @@
|
||||
-- 平台管理员用户表补充生日字段(yz_system_admin_user)
|
||||
-- 用途:/platform/editUser/:id 支持 birth,/platform/getUserInfo/:id 返回 birth
|
||||
ALTER TABLE `yz_system_admin_user`
|
||||
ADD COLUMN `birth` varchar(20) DEFAULT NULL COMMENT '生日' AFTER `sex`;
|
||||
@@ -1,4 +1,3 @@
|
||||
-- 会话表增加置顶字段
|
||||
ALTER TABLE `yz_platform_ai_chat_session`
|
||||
ADD COLUMN `is_top` tinyint NOT NULL DEFAULT 0 COMMENT '是否置顶 1-是' AFTER `model`,
|
||||
ADD KEY `idx_is_top` (`is_top`);
|
||||
@@ -1,4 +1,2 @@
|
||||
-- 平台 AI 服务商配置增加协议类型字段
|
||||
-- api_type: chat_completions(OpenAI Chat Completions) / responses(OpenAI Responses) / anthropic(Anthropic Messages)
|
||||
ALTER TABLE `yz_platform_ai_provider`
|
||||
ADD COLUMN `api_type` varchar(30) NOT NULL DEFAULT 'chat_completions' COMMENT '协议类型' AFTER `provider_type`;
|
||||
@@ -1,5 +1,2 @@
|
||||
-- 服务号配置表补充「关注二维码」字段(未认证公众号无带参二维码,
|
||||
-- 平台端上传普通关注二维码图片,绑定页展示供用户扫码关注后发送「验证码」绑定)
|
||||
-- 存储格式:data URL(data:image/png;base64,...),前端可直接作为 <img> 源
|
||||
ALTER TABLE `yz_platform_wechat_mp_config`
|
||||
ADD COLUMN `follow_qrcode` longtext NULL COMMENT '公众号关注二维码图片(data URL)' AFTER `remark`;
|
||||
@@ -1,19 +1,3 @@
|
||||
-- =============================================================
|
||||
-- yz_system_menu 增加「是否必须登录」字段 require_login
|
||||
--
|
||||
-- 用途:免登录控制从模块级下沉到菜单级——Platform 菜单管理逐条配置
|
||||
-- 某菜单(功能入口)是否允许移动端游客(持游客令牌)免登录使用。
|
||||
-- 1 = 必须登录(默认,保持既有行为)
|
||||
-- 0 = 可免登录使用(进入 nav 公开菜单 /api/menus/public)
|
||||
--
|
||||
-- 关联:yz_system_modules.require_login 保留但移动端不再作为判定依据,
|
||||
-- 以菜单级开关为准(模块宫格是否可点 = 该模块下存在免登录菜单)。
|
||||
--
|
||||
-- 幂等:MySQL 的 ALTER TABLE ADD COLUMN 不支持 IF NOT EXISTS,
|
||||
-- 重复执行会报 1060 Duplicate column name。这里用 information_schema
|
||||
-- 判断列是否存在,缺失才拼 ADD COLUMN,再通过 PREPARE 执行。
|
||||
-- 约定:本脚本在 mysql 客户端手动执行(同一会话保持 PREPARE 生效)。
|
||||
-- =============================================================
|
||||
|
||||
SET @sql := CONCAT(
|
||||
'ALTER TABLE `yz_system_menu` ',
|
||||
@@ -27,23 +11,9 @@ SET @sql := CONCAT(
|
||||
)
|
||||
);
|
||||
|
||||
-- 列已存在时 @sql 仅剩 'ALTER TABLE `yz_system_menu` ',替换为无害语句
|
||||
SET @sql := IF(RIGHT(TRIM(@sql), 1) = '`', 'SELECT 1 AS column_already_exists', @sql);
|
||||
|
||||
PREPARE stmt FROM @sql;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- =============================================================
|
||||
-- 初始放开「便捷工具」的三个免登录功能(确认菜单标题后再执行):
|
||||
--
|
||||
-- SELECT id, title, path FROM `yz_system_menu`
|
||||
-- WHERE title IN ('记事本', '日程提醒', '账号管理') AND delete_time IS NULL;
|
||||
--
|
||||
-- UPDATE `yz_system_menu`
|
||||
-- SET `require_login` = 0
|
||||
-- WHERE title IN ('记事本', '日程提醒', '账号管理');
|
||||
--
|
||||
-- 说明:父级目录菜单如需游客可见,也要一并置 0;
|
||||
-- 后续新模块按需放开,全部走 Platform 菜单管理界面配置。
|
||||
-- =============================================================
|
||||
@@ -1,15 +1,3 @@
|
||||
-- =============================================================
|
||||
-- yz_system_modules 增加「是否必须登录」字段 require_login
|
||||
--
|
||||
-- 用途:Platform 模块管理可配置某业务模块是否允许移动端免登录访问。
|
||||
-- 1 = 必须登录(默认,保持既有行为)
|
||||
-- 0 = 可免登录使用
|
||||
--
|
||||
-- 幂等:MySQL 的 ALTER TABLE ADD COLUMN 不支持 IF NOT EXISTS,
|
||||
-- 重复执行会报 1060 Duplicate column name。这里用 information_schema
|
||||
-- 判断列是否存在,缺失才拼 ADD COLUMN,再通过 PREPARE 执行。
|
||||
-- 约定:本脚本在 mysql 客户端手动执行(同一会话保持 PREPARE 生效)。
|
||||
-- =============================================================
|
||||
|
||||
SET @sql := CONCAT(
|
||||
'ALTER TABLE `yz_system_modules` ',
|
||||
@@ -23,24 +11,9 @@ SET @sql := CONCAT(
|
||||
)
|
||||
);
|
||||
|
||||
-- 列已存在时 @sql 仅剩 'ALTER TABLE `yz_system_modules` ',替换为无害语句
|
||||
SET @sql := IF(RIGHT(TRIM(@sql), 1) = '`', 'SELECT 1 AS column_already_exists', @sql);
|
||||
|
||||
PREPARE stmt FROM @sql;
|
||||
EXECUTE stmt;
|
||||
DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- =============================================================
|
||||
-- 方案 B(兜底):不支持会话变量 / PREPARE 的执行器(工单系统等),
|
||||
-- 改用下面的纯静态语句。注意:本条不幂等,列已存在会报
|
||||
-- 1060 Duplicate column,执行前先用 information_schema 自查:
|
||||
--
|
||||
-- SELECT COUNT(*) FROM information_schema.COLUMNS
|
||||
-- WHERE TABLE_SCHEMA = DATABASE()
|
||||
-- AND TABLE_NAME = 'yz_system_modules'
|
||||
-- AND COLUMN_NAME = 'require_login'; -- 返回 0 才执行 ALTER
|
||||
--
|
||||
-- ALTER TABLE `yz_system_modules`
|
||||
-- ADD COLUMN `require_login` TINYINT NOT NULL DEFAULT 1
|
||||
-- COMMENT '1=必须登录 0=可免登录使用' AFTER `is_show`;
|
||||
-- =============================================================
|
||||
@@ -1,12 +1,3 @@
|
||||
-- 微信小程序多应用表补充「消息推送」配置字段
|
||||
--
|
||||
-- 对应小程序后台:开发管理 → 开发设置 → 消息推送
|
||||
-- Token / EncodingAESKey / 消息加解密方式 / 数据格式
|
||||
-- 平台端「小程序配置 - 编辑小程序 - 消息推送」维护,保存后把「回调地址」填到后台。
|
||||
--
|
||||
-- 注意:aes_key 以 AES-256-GCM 加密存储(复用 wechatmp 的密钥),与 AppSecret 同一套加密。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < alter_wechat_mini_app_push.sql
|
||||
-- ============================================================
|
||||
|
||||
ALTER TABLE `yz_platform_wechat_mini_app`
|
||||
ADD COLUMN `token` varchar(128) NOT NULL DEFAULT '' COMMENT '消息推送 Token(小程序后台「消息推送」填写)' AFTER `qrcode_url`,
|
||||
@@ -15,7 +6,6 @@ ALTER TABLE `yz_platform_wechat_mini_app`
|
||||
ADD COLUMN `data_format` varchar(16) NOT NULL DEFAULT 'xml' COMMENT '消息数据格式 xml / json' AFTER `encrypt_mode`,
|
||||
ADD COLUMN `push_reply` varchar(512) NOT NULL DEFAULT '' COMMENT '客服消息自动回复文案(空=不自动回复)' AFTER `data_format`;
|
||||
|
||||
-- 结果校验
|
||||
SELECT id, name, app_id, enabled, token, encrypt_mode, data_format, push_reply
|
||||
FROM yz_platform_wechat_mini_app
|
||||
WHERE delete_time IS NULL;
|
||||
@@ -1,11 +1,6 @@
|
||||
-- 微信小程序多应用表补充「小程序码」字段
|
||||
-- 平台端「小程序配置 - 新增/编辑小程序」上传并保存二维码图片地址,
|
||||
-- 官网 / H5 等其他端通过 GET /site/miniapp 读取 qrcode_url 展示。
|
||||
-- 存储格式:上传后的访问地址(本地为 /uploads/...,七牛为 CDN 绝对地址)
|
||||
ALTER TABLE `yz_platform_wechat_mini_app`
|
||||
ADD COLUMN `qrcode_url` varchar(512) NOT NULL DEFAULT '' COMMENT '小程序码图片地址(供官网/H5等其他端调取)' AFTER `app_secret`;
|
||||
|
||||
-- 结果校验
|
||||
SELECT id, name, app_id, enabled, qrcode_url
|
||||
FROM yz_platform_wechat_mini_app
|
||||
WHERE delete_time IS NULL;
|
||||
@@ -1,23 +1,10 @@
|
||||
-- ============================================================
|
||||
-- CRM 招投标管理 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < bidding_menus.sql
|
||||
-- ============================================================
|
||||
|
||||
-- 菜单表字段说明(yz_system_menu)
|
||||
-- type: 1=目录菜单,2=页面菜单
|
||||
-- pid : 父菜单ID
|
||||
-- views: 可见端标识,沿用父级 '[2]'(后台)
|
||||
-- is_visible / status: 1 表示显示并启用
|
||||
|
||||
-- 顶层入口「招投标」已存在:path = '/apps/crm/bidding'
|
||||
SET @bidding_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
WHERE path = '/apps/crm/bidding' AND delete_time IS NULL
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 一级子页面 ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @bidding_id, '我要投标', '/apps/crm/bidding/bid', 'apps/crm/bidding/bid/index.vue',
|
||||
@@ -34,7 +21,6 @@ FROM DUAL
|
||||
WHERE @bidding_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/crm/bidding/tender' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 公共资料库(目录 + 两个页面) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @bidding_id, '公共资料库', '/apps/crm/bidding/library', NULL,
|
||||
@@ -65,7 +51,6 @@ FROM DUAL
|
||||
WHERE @library_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/crm/bidding/library/qualification' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 统计报表(目录 + 两个页面) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @bidding_id, '统计报表', '/apps/crm/bidding/statistics', NULL,
|
||||
@@ -96,7 +81,6 @@ FROM DUAL
|
||||
WHERE @stats_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/crm/bidding/statistics/bid' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, type, sort
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path LIKE '/apps/crm/bidding%'
|
||||
|
||||
@@ -1,11 +1,3 @@
|
||||
-- 清理「注册未完成」的残留身份(历史遗留)。
|
||||
-- 旧版本在第一步核验通过时就建号,第二步企业归属超时未完成时,
|
||||
-- 账号名/手机号被占用却无法使用,重新注册会提示「该账号已被占用」。
|
||||
-- 新版本已做到:第二步才建号 + 令牌过期回滚 + 校验时自动回收孤儿身份,
|
||||
-- 本脚本仅用于手动清理历史残留(注意:account / mobile 有唯一索引,
|
||||
-- 软删仍然占着索引,因此这里用物理删除)。
|
||||
--
|
||||
-- ① 先查:确认这些身份确实没企业归属、也没登录过
|
||||
SELECT i.id, i.account, i.mobile, i.nickname, i.create_time
|
||||
FROM yz_auth_identity i
|
||||
WHERE i.last_login_at IS NULL
|
||||
@@ -18,7 +10,6 @@ WHERE i.last_login_at IS NULL
|
||||
WHERE a.identity_id = i.id AND a.delete_time IS NULL
|
||||
);
|
||||
|
||||
-- ② 再清:把 '账号名' 换成第①步查到的账号(手机号注册则改用 mobile = '手机号')
|
||||
DELETE FROM yz_auth_identity_third
|
||||
WHERE identity_id IN (
|
||||
SELECT id FROM (SELECT id FROM yz_auth_identity WHERE account = '账号名') x
|
||||
|
||||
@@ -1,14 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 审批流功能绑定(biz_type ↔ flow 多对多关联)
|
||||
--
|
||||
-- 对应模型:go/models/approval.go ApprovalBinding
|
||||
-- 用途:给某个功能(biz_type)绑定"可选审批流"清单,业务代码通过
|
||||
-- ListAvailableFlows(scope, tid, bizType, userOrgID) 拿到过滤后的
|
||||
-- 可用流;若一条流程设置了 apply_dept_ids,则仅该部门成员可见。
|
||||
--
|
||||
-- 注意:本表**不含条件表达式 / 优先级**——条件分支在流程内部(条件网关)
|
||||
-- 实现,与绑定层无关。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
@@ -1,23 +1,6 @@
|
||||
-- =============================================================
|
||||
-- 自定义审批流(租户侧 + 平台侧)
|
||||
--
|
||||
-- 对应模型:go/models/approval.go
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 配置侧与实例侧分离:flow/node 是配置(租户可编辑),
|
||||
-- instance/task 是运行时(提交后生成,不可编辑)。
|
||||
-- 2. 节点表用 prev_keys / next_keys 存连线,当期顺序链只填 sort,
|
||||
-- 后续上拖拽图与条件分支无需改表。
|
||||
-- 3. scope 区分租户侧(tenant)与平台侧(platform):平台账号不归属租户,
|
||||
-- 其流程不带 tid,实例用 biz_tid 标记申请来源租户。
|
||||
--
|
||||
-- 注意:不显式指定 COLLATE,沿用数据库默认排序规则,避免与既有表
|
||||
-- (utf8mb4_0900_ai_ci)在 JOIN 比较字符串时报 Illegal mix of collations。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 租户侧审批流程 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_approval_flow` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -40,7 +23,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_approval_flow` (
|
||||
KEY `idx_tid_code` (`tid`,`flow_code`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-自定义审批流程(租户侧)';
|
||||
|
||||
-- ---------------- 2. 租户侧审批节点 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_approval_node` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`flow_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '所属流程ID',
|
||||
@@ -69,7 +51,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_approval_node` (
|
||||
KEY `idx_flow_sort` (`flow_id`,`sort`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-自定义审批节点(租户侧)';
|
||||
|
||||
-- ---------------- 3. 平台侧审批流程 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_approval_flow` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`module_code` VARCHAR(50) NOT NULL DEFAULT '' COMMENT '所属平台模块 code',
|
||||
@@ -89,7 +70,6 @@ CREATE TABLE IF NOT EXISTS `yz_platform_approval_flow` (
|
||||
KEY `idx_code` (`flow_code`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='平台-自定义审批流程';
|
||||
|
||||
-- ---------------- 4. 平台侧审批节点 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_approval_node` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`flow_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '所属流程ID',
|
||||
@@ -116,7 +96,6 @@ CREATE TABLE IF NOT EXISTS `yz_platform_approval_node` (
|
||||
KEY `idx_flow_sort` (`flow_id`,`sort`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='平台-自定义审批节点';
|
||||
|
||||
-- ---------------- 5. 审批实例(运行时,租户侧与平台侧共用) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_approval_instance` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`scope` TINYINT NOT NULL DEFAULT 1 COMMENT '1租户侧 2平台侧',
|
||||
@@ -146,7 +125,6 @@ CREATE TABLE IF NOT EXISTS `yz_approval_instance` (
|
||||
KEY `idx_flow` (`flow_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='审批实例(运行时)';
|
||||
|
||||
-- ---------------- 6. 审批任务(运行时,节点级待办) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_approval_task` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`instance_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '实例ID',
|
||||
@@ -176,24 +154,3 @@ CREATE TABLE IF NOT EXISTS `yz_approval_task` (
|
||||
KEY `idx_tid` (`tid`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='审批任务(运行时·待办)';
|
||||
|
||||
-- =============================================================
|
||||
-- 旧表迁移说明:
|
||||
-- yz_backend_approval_flows(扁平步骤行结构)仅被 OA 报销 Submit 读取。
|
||||
-- 第一期接管报销后改走新引擎,旧表保留只读兼容,不再写入。
|
||||
-- 如需保留历史配置,可按如下语句转换(按需执行):
|
||||
--
|
||||
-- INSERT INTO yz_backend_approval_flow
|
||||
-- (tid, module_code, biz_type, flow_name, is_default, status)
|
||||
-- SELECT DISTINCT tid, 'oa', 'reimburse', flow_name, 1, 1
|
||||
-- FROM yz_backend_approval_flows
|
||||
-- WHERE is_active = 1 AND is_deleted = 0
|
||||
-- GROUP BY tid, flow_name;
|
||||
--
|
||||
-- INSERT INTO yz_backend_approval_node
|
||||
-- (flow_id, tid, node_key, node_name, node_type, approver_type, approver_ids, timeout_hours, sort)
|
||||
-- SELECT f.id, f.tid, CONCAT('step_', s.step_order), s.flow_name, 2, 2, '', s.timeout_hours, s.step_order
|
||||
-- FROM yz_backend_approval_flows s
|
||||
-- JOIN yz_backend_approval_flow f
|
||||
-- ON f.tid = s.tid AND f.biz_type = 'reimburse'
|
||||
-- WHERE s.is_active = 1 AND s.is_deleted = 0;
|
||||
-- =============================================================
|
||||
@@ -1,8 +1,3 @@
|
||||
-- 微信小程序扫码注册核验会话:
|
||||
-- PC 注册页发起会话并展示小程序码(scene)→ 用户微信扫码进入小程序「注册确认」页 →
|
||||
-- 小程序端 wx.login 拿 code(可选手机号快速验证)调 /auth/register/mini/confirm →
|
||||
-- 服务端 code2session 得 openid/unionid 写入本表 → PC 端轮询到已确认后继续注册,
|
||||
-- 第一步核验(mode=mini)按 scene 核销并取出 openid(注册完成后绑定小程序登录)。
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_mini_register` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`scene` VARCHAR(64) NOT NULL COMMENT '注册会话标识(小程序码 scene)',
|
||||
|
||||
@@ -1,8 +1,3 @@
|
||||
-- 统一认证:注册会话(第一步核验 → 第二步企业归属)
|
||||
-- 之前注册会话只存在进程内存里,服务重启 / 多副本部署 / 填表超时都会导致
|
||||
-- 「注册会话已失效,请重新注册」。改为落库后:
|
||||
-- ① 重启、多实例共享都不丢;② 有效期可放宽到 2 小时(填企业资料+上传执照足够);
|
||||
-- ③ 身份仍在第二步才创建,超时/放弃时不会留下占用账号的半成品身份。
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_register_session` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`token` VARCHAR(64) NOT NULL COMMENT '注册令牌(第一步核验通过后签发)',
|
||||
|
||||
@@ -1,19 +1,6 @@
|
||||
-- =============================================================
|
||||
-- 统一认证中心(UAC)表结构 数据库:go-platform
|
||||
-- 路径:api.yunzer.cn/auth
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. yz_auth_identity 为「自然人」层,密码上提到这一层;
|
||||
-- 2. yz_auth_tenant_user 为「身份-企业」绑定,一人可在多家企业任职;
|
||||
-- 3. 密码列存 PHC 格式($argon2id$...),盐内联,无需独立 salt 列;
|
||||
-- 历史数据为 salt$sha256(legacy),首次登录时自动升级;
|
||||
-- 4. 会话/刷新令牌/授权码均存哈希,明文不下发到数据库;
|
||||
-- 5. 本脚本只建表不写数据,数据迁移由 scripts/migrate_auth.go 完成。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 统一身份(自然人) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_identity` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '身份ID',
|
||||
`union_id` VARCHAR(32) NOT NULL COMMENT '全局唯一标识(32位随机串)',
|
||||
@@ -42,7 +29,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_identity` (
|
||||
KEY `idx_create_time` (`create_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-身份表';
|
||||
|
||||
-- ---------------- 2. 身份-企业绑定(一人多企) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_tenant_user` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL COMMENT '租户ID',
|
||||
@@ -65,7 +51,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_tenant_user` (
|
||||
KEY `idx_tid_status` (`tid`, `status`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-身份企业绑定';
|
||||
|
||||
-- ---------------- 3. 接入应用(OIDC Client) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_client` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`client_id` VARCHAR(64) NOT NULL,
|
||||
@@ -89,7 +74,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_client` (
|
||||
UNIQUE KEY `uk_app_code` (`app_code`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-接入应用';
|
||||
|
||||
-- ---------------- 4. 登录会话(1号1机 / 强制下线) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_session` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`sid` VARCHAR(64) NOT NULL COMMENT '会话ID,写入JWT的sid',
|
||||
@@ -115,7 +99,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_session` (
|
||||
KEY `idx_expires` (`expires_at`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-登录会话';
|
||||
|
||||
-- ---------------- 5. 刷新令牌(轮换 + 重放检测) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_refresh_token` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`token_hash` VARCHAR(128) NOT NULL COMMENT '不透明串的哈希,明文不下发落库',
|
||||
@@ -136,7 +119,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_refresh_token` (
|
||||
KEY `idx_expires` (`expires_at`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-刷新令牌';
|
||||
|
||||
-- ---------------- 6. 授权码(一次性,60秒) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_code` (
|
||||
`code_hash` VARCHAR(128) NOT NULL COMMENT '授权码哈希',
|
||||
`client_id` VARCHAR(64) NOT NULL,
|
||||
@@ -154,7 +136,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_code` (
|
||||
KEY `idx_expires` (`expires_at`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-授权码';
|
||||
|
||||
-- ---------------- 7. 令牌吊销表(登出/踢下线) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_token_blacklist` (
|
||||
`jti` VARCHAR(64) NOT NULL COMMENT 'JWT ID',
|
||||
`identity_id` BIGINT UNSIGNED NOT NULL DEFAULT 0,
|
||||
@@ -166,7 +147,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_token_blacklist` (
|
||||
KEY `idx_expires` (`expires_at`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-令牌吊销表';
|
||||
|
||||
-- ---------------- 8. 第三方身份绑定 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_identity_third` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`identity_id` BIGINT UNSIGNED NOT NULL,
|
||||
@@ -182,7 +162,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_identity_third` (
|
||||
KEY `idx_identity` (`identity_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-第三方绑定';
|
||||
|
||||
-- ---------------- 9. 租户自带身份源(企业微信/钉钉/飞书/OIDC) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_tenant_idp` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL,
|
||||
@@ -205,7 +184,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_tenant_idp` (
|
||||
UNIQUE KEY `uk_tid_provider` (`tid`, `provider`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-租户身份源';
|
||||
|
||||
-- ---------------- 10. 租户登录策略 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_tenant_auth_config` (
|
||||
`tid` BIGINT UNSIGNED NOT NULL COMMENT '租户ID',
|
||||
`verify_type` VARCHAR(20) NOT NULL DEFAULT 'captcha' COMMENT 'none/captcha/sms/email/geetest',
|
||||
@@ -222,7 +200,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_tenant_auth_config` (
|
||||
PRIMARY KEY (`tid`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-租户登录策略';
|
||||
|
||||
-- ---------------- 11. 统一登录日志 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_auth_login_log` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED DEFAULT NULL,
|
||||
@@ -245,10 +222,6 @@ CREATE TABLE IF NOT EXISTS `yz_auth_login_log` (
|
||||
KEY `idx_create_time` (`create_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='统一认证-登录日志';
|
||||
|
||||
-- =============================================================
|
||||
-- 内置接入应用(后续由 platform 端「应用注册」页面维护)
|
||||
-- client_secret 为占位值,正式启用前必须在管理端重新生成
|
||||
-- =============================================================
|
||||
INSERT INTO `yz_auth_client`
|
||||
(`client_id`, `app_code`, `name`, `app_type`, `grant_types`, `scope`, `access_ttl`, `refresh_ttl`, `realm`)
|
||||
VALUES
|
||||
|
||||
@@ -1,13 +1,4 @@
|
||||
-- ============================================================
|
||||
-- 注册企业绑定/创建申请(yz_auth_tenant_apply)+ 审核菜单
|
||||
-- type=1 加入企业:注册第二步「绑定企业」,企业管理员在 backend 审批
|
||||
-- type=2 创建企业:注册第二步「创建企业」,平台在 platform 审批,
|
||||
-- 通过后自动建租户并把申请人绑定为租户管理员(不可更改)
|
||||
-- 幂等脚本:重复执行不会产生重复数据。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < create_auth_tenant_apply.sql
|
||||
-- ============================================================
|
||||
|
||||
-- ---------- 1. 申请表 ----------
|
||||
CREATE TABLE IF NOT EXISTS yz_auth_tenant_apply (
|
||||
id bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
identity_id bigint unsigned NOT NULL COMMENT '申请人统一身份ID(yz_auth_identity)',
|
||||
@@ -35,8 +26,6 @@ CREATE TABLE IF NOT EXISTS yz_auth_tenant_apply (
|
||||
KEY idx_apply_status (status, type)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='注册时加入企业/创建企业申请';
|
||||
|
||||
-- ---------- 2. backend 菜单:基础设置 → 加入申请 ----------
|
||||
-- 注意:用户变量在 SELECT 列表赋值后于同语句 WHERE 中引用不可靠,改用派生表
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT bs.id, '加入申请', '/basicSettings/applies', 'basicSettings/applies/index.vue',
|
||||
@@ -44,7 +33,6 @@ SELECT bs.id, '加入申请', '/basicSettings/applies', 'basicSettings/applies/i
|
||||
FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL LIMIT 1) bs
|
||||
WHERE NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/applies' AND delete_time IS NULL) x);
|
||||
|
||||
-- 找不到基础设置目录时退化为 backend 顶级菜单
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT 0, '加入申请', '/basicSettings/applies', 'basicSettings/applies/index.vue',
|
||||
@@ -53,7 +41,6 @@ FROM DUAL
|
||||
WHERE (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL LIMIT 1) IS NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/applies' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 3. platform 菜单:企业创建审核(顶级) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT 0, '企业创建审核', '/tenantApply', 'tenantApply/index.vue',
|
||||
@@ -61,13 +48,10 @@ SELECT 0, '企业创建审核', '/tenantApply', 'tenantApply/index.vue',
|
||||
FROM DUAL
|
||||
WHERE NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/tenantApply' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 4. 把「加入申请」菜单加入全局「租户管理员」角色 rights ----------
|
||||
-- rights 兼容 JSON 数组与逗号分隔两种格式;rights 为空表示全权限,无需处理
|
||||
SET @apply_menu_id := (
|
||||
SELECT id FROM yz_system_menu WHERE path = '/basicSettings/applies' AND delete_time IS NULL LIMIT 1
|
||||
);
|
||||
|
||||
-- 逗号分隔格式:追加
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CONCAT(TRIM(TRAILING ',' FROM TRIM(BOTH ' ' FROM rights)), ',', @apply_menu_id)
|
||||
WHERE cid = 2 AND tenant_id = 0 AND name = '租户管理员' AND delete_time IS NULL
|
||||
@@ -75,7 +59,6 @@ WHERE cid = 2 AND tenant_id = 0 AND name = '租户管理员' AND delete_time IS
|
||||
AND rights IS NOT NULL AND TRIM(rights) <> '' AND TRIM(rights) NOT LIKE '[%'
|
||||
AND NOT FIND_IN_SET(@apply_menu_id, REPLACE(REPLACE(REPLACE(rights, '[', ''), ']', ''), ' ', ''));
|
||||
|
||||
-- JSON 数组格式:末尾插入
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CONCAT(SUBSTRING(TRIM(rights), 1, LENGTH(TRIM(rights)) - 1), ',', @apply_menu_id, ']')
|
||||
WHERE cid = 2 AND tenant_id = 0 AND name = '租户管理员' AND delete_time IS NULL
|
||||
@@ -83,7 +66,6 @@ WHERE cid = 2 AND tenant_id = 0 AND name = '租户管理员' AND delete_time IS
|
||||
AND TRIM(rights) LIKE '[%' AND TRIM(rights) LIKE '%]'
|
||||
AND NOT FIND_IN_SET(@apply_menu_id, REPLACE(REPLACE(REPLACE(rights, '[', ''), ']', ''), ' ', ''));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, views, type
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path IN ('/basicSettings/applies', '/tenantApply');
|
||||
|
||||
@@ -1,28 +1,6 @@
|
||||
-- =============================================================
|
||||
-- CRM 招投标管理模块表结构(17 张)
|
||||
--
|
||||
-- 模块说明:CRM 系统下的「招投标管理」子模块
|
||||
-- - 我要招标(甲方):6 张表
|
||||
-- - 我要投标(乙方):11 张表
|
||||
-- 设计原则:
|
||||
-- 1. 命名统一以 yz_backend_crm_bidding_ 为前缀
|
||||
-- 2. 软删除:delete_time
|
||||
-- 3. 多租户:tenant_id
|
||||
-- 4. 与现有 CRM 模块(business/contract/project)字段风格一致
|
||||
-- 5. 中标/定标后只存 ID 引用(contract_id、project_id),不冗余数据
|
||||
--
|
||||
-- 状态机:
|
||||
-- 招标:0草稿 -> 1公告中 -> 2报名中 -> 3投标中 -> 4开标中 -> 5评标中 -> 6已定标 -> 7已归档
|
||||
-- 投标:0草稿 -> 1立项审批中 -> 2投标中 -> 3已开标 -> (4中标 | 5落标) -> (6已转合同 | 7已归档)
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ============================================================
|
||||
-- 第一部分:我要招标(6 张)
|
||||
-- ============================================================
|
||||
|
||||
-- ---------------- 1. 招标项目主表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -73,7 +51,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-招标项目主表';
|
||||
|
||||
-- ---------------- 2. 招标文件表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_file` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -94,7 +71,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_file` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-招标文件';
|
||||
|
||||
-- ---------------- 3. 招标公告表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_announce` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -116,7 +92,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_announce` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-招标公告';
|
||||
|
||||
-- ---------------- 4. 投标方/供应商表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_supplier` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -144,7 +119,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_supplier` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标方/供应商';
|
||||
|
||||
-- ---------------- 5. 开标评标表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_evaluation` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -172,7 +146,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_evaluation` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-开标评标';
|
||||
|
||||
-- ---------------- 6. 定标结果表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_result` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -196,12 +169,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_tender_result` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-定标结果';
|
||||
|
||||
|
||||
-- ============================================================
|
||||
-- 第二部分:我要投标(11 张)
|
||||
-- ============================================================
|
||||
|
||||
-- ---------------- 7. 投标项目主表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -260,7 +227,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标项目主表';
|
||||
|
||||
-- ---------------- 8. 投标文件表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_file` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -282,7 +248,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_file` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标文件';
|
||||
|
||||
-- ---------------- 9. 投标立项审批表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_approval` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -308,7 +273,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_approval` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标立项审批';
|
||||
|
||||
-- ---------------- 10. 投标任务表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_task` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -337,7 +301,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_task` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标任务';
|
||||
|
||||
-- ---------------- 11. 标书模板表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_template` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -359,7 +322,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_template` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-标书模板';
|
||||
|
||||
-- ---------------- 12. 标书版本表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_document` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -387,7 +349,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_document` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-标书版本';
|
||||
|
||||
-- ---------------- 13. 资质文件库 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_qualification` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -415,7 +376,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_qualification` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-资质文件库';
|
||||
|
||||
-- ---------------- 14. 报价表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_quote` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -444,7 +404,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_quote` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-报价表';
|
||||
|
||||
-- ---------------- 15. 竞争对手报价表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_competitor` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -466,7 +425,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_competitor` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-竞争对手报价';
|
||||
|
||||
-- ---------------- 16. 投标结果表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_result` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -491,7 +449,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_result` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标结果';
|
||||
|
||||
-- ---------------- 17. 投标费用表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_expense` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -517,10 +474,3 @@ CREATE TABLE IF NOT EXISTS `yz_backend_crm_bidding_bid_expense` (
|
||||
KEY `idx_delete_time` (`delete_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='CRM-投标费用';
|
||||
|
||||
|
||||
-- ============================================================
|
||||
-- 菜单配置(投标管理)
|
||||
-- ============================================================
|
||||
-- 招标方菜单:path = 'apps/crm/bidding/tender/index.vue'
|
||||
-- 投标方菜单:path = 'apps/crm/bidding/bid/index.vue'
|
||||
-- 注意:菜单通常通过平台端 UI 配置,详见 docs/bidding_menus.sql
|
||||
@@ -1,39 +1,6 @@
|
||||
-- =============================================================
|
||||
-- 数据字典 —— 平台端 / 租户端各一套
|
||||
--
|
||||
-- 表清单:
|
||||
-- yz_platform_dict 平台端「字典列表」(字典类型)
|
||||
-- yz_platform_dict_item 平台端「字典项」
|
||||
-- yz_backend_dict 租户端「字典列表」(按 tenant_id 租户隔离)
|
||||
-- yz_backend_dict_item 租户端「字典项」
|
||||
--
|
||||
-- 设计说明:
|
||||
-- 1. 平台端字典与租户端字典完全独立:平台端字典供平台系统自身使用
|
||||
-- (不按租户隔离);租户端字典是每个租户可自行维护的业务选项
|
||||
-- (如供应商类型、结算方式),按 tenant_id 隔离,与
|
||||
-- yz_backend_erp_supplier 的隔离方式保持一致。
|
||||
-- 2. 字典项通过 dict_id 关联字典;租户端额外冗余 tenant_id,
|
||||
-- 便于不带 JOIN 直接按租户过滤,写入时须与父字典 tenant_id 一致。
|
||||
-- 3. tag_type 对应前端 el-tag 的 type(primary/success/warning/danger/info),
|
||||
-- 留空表示该项在列表里不渲染彩色标签。
|
||||
-- 4. 与 yz_backend_erp_* / yz_backend_crm_* 等表一致,这里只建普通索引、
|
||||
-- 不建唯一索引:一是软删除(delete_time)后编码仍会占用唯一键,
|
||||
-- 二是库中既有表也普遍不用唯一索引。dict_code / item_value 的唯一性
|
||||
-- 由后端接口在写入时校验。
|
||||
-- 5. 不显式指定 COLLATE,沿用库默认排序规则,避免 JOIN 时报
|
||||
-- Illegal mix of collations。
|
||||
--
|
||||
-- 执行方式:人工在数据库执行,代码中不做任何自动建表 / 补列。
|
||||
-- 说明:下方 DDL 幂等(IF NOT EXISTS),可重复执行。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 平台端
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_dict` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID',
|
||||
`dict_name` VARCHAR(100) NOT NULL DEFAULT '' COMMENT '字典名称,如:供应商类型',
|
||||
@@ -50,7 +17,6 @@ CREATE TABLE IF NOT EXISTS `yz_platform_dict` (
|
||||
KEY `idx_status_sort` (`status`, `sort`, `id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='平台端-数据字典(字典列表)';
|
||||
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_dict_item` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID',
|
||||
`dict_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '所属字典ID(yz_platform_dict.id)',
|
||||
@@ -69,11 +35,6 @@ CREATE TABLE IF NOT EXISTS `yz_platform_dict_item` (
|
||||
KEY `idx_dict_value` (`dict_id`, `item_value`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='平台端-字典项';
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 租户端(按 tenant_id 隔离)
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_dict` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID',
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID(同 yz_backend_erp_supplier.tenant_id)',
|
||||
@@ -91,7 +52,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_dict` (
|
||||
KEY `idx_tenant_status_sort` (`tenant_id`, `status`, `sort`, `id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='租户端-数据字典(字典列表)';
|
||||
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_dict_item` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID',
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID,须与所属字典一致',
|
||||
|
||||
@@ -1,11 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 游客(免登录模块)身份与通用数据表
|
||||
-- 对应代码:models.GuestUser / models.GuestData、services/gueststore
|
||||
-- 幂等:CREATE TABLE IF NOT EXISTS,可重复执行
|
||||
-- 用途:小程序用手机号授权换取“游客轻身份”,免登录模块产生的数据
|
||||
-- 按 guest_id + module 存入 yz_guest_data(文档式,永久保留不清理);
|
||||
-- 正式登录后按手机号把数据合并进正式账号(merged_uid 标记,行置 is_deleted=2)。
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_guest_user` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
|
||||
@@ -1,25 +1,3 @@
|
||||
-- =============================================================
|
||||
-- OA 考勤打卡 —— 表结构
|
||||
--
|
||||
-- 对应代码:
|
||||
-- models/oa_attendance.go
|
||||
-- controllers/backend_oa_attendance.go (打卡核心 + 后台考勤记录)
|
||||
-- controllers/app_oa_attendance.go (移动端 /api/oa/attendance/*)
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) 本脚本:创建考勤表
|
||||
-- 2) oa_attendance_menus.sql:注册「OA → 排班考勤 → 考勤记录 / 考勤打卡」菜单
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 一人一天一条:签到与签退写同一行,统计与列表都按「人 × 日期」聚合。
|
||||
-- 2. 打卡时联动排班明细(yz_backend_oa_schedule_entry),把班次名称与
|
||||
-- 上下班时间快照进本表;后续调班不影响历史考勤判定。
|
||||
-- 3. 匹配不上排班(含员工档案缺失)不阻断打卡:match_status=2,
|
||||
-- clock_in_status/clock_out_status=3(无排班打卡),提醒文案落在
|
||||
-- clock_in_note / clock_out_note,后台可据此筛选与备注。
|
||||
-- 4. 唯一键 (tid, uid, attend_date):uid 是登录身份,保证员工档案未建
|
||||
-- 也能先打卡(此时 employee_id=0,后台按账号/姓名检索)。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
@@ -61,7 +39,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_attendance` (
|
||||
KEY `idx_tid_status` (`tid`, `clock_in_status`, `clock_out_status`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-考勤打卡记录';
|
||||
|
||||
-- ---------------- 校验 ----------------
|
||||
SELECT TABLE_NAME, TABLE_COMMENT
|
||||
FROM information_schema.TABLES
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
|
||||
@@ -1,17 +1,6 @@
|
||||
-- =============================================================
|
||||
-- OA 薪酬管理模块表结构
|
||||
--
|
||||
-- 说明:代码里有模型定义(models/backend_oa_compensation.go),
|
||||
-- 但此前缺少建表脚本,访问薪酬页面会因表不存在返回 500。
|
||||
-- 本脚本补齐三张表,仅新建、不改动任何既有数据。
|
||||
--
|
||||
-- 注意:不显式指定 COLLATE,沿用数据库默认排序规则,避免与既有表
|
||||
-- (utf8mb4_0900_ai_ci)在 JOIN 比较字符串时报 Illegal mix of collations。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 员工薪酬方案 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_compensation_schemes` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -42,7 +31,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_compensation_schemes` (
|
||||
KEY `idx_effective` (`effective_date`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-员工薪酬方案';
|
||||
|
||||
-- ---------------- 2. 月度薪资单主表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_compensation_payrolls` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -84,7 +72,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_compensation_payrolls` (
|
||||
KEY `idx_status` (`status`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-月度薪资单';
|
||||
|
||||
-- ---------------- 3. 薪资单自定义增减项 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_compensation_payroll_items` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
|
||||
@@ -1,26 +1,6 @@
|
||||
-- =============================================================
|
||||
-- OA 工作日报 —— 表结构
|
||||
--
|
||||
-- 对应代码:
|
||||
-- models/oa_daily_report.go
|
||||
-- services/oauth/dailyreport_service.go
|
||||
-- controllers/backend_oa_dailyreport.go(后台 PC 端)
|
||||
-- controllers/app_oa_dailyreport.go(小程序端)
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 每人每天一条日报,用 (tid, user_id, report_date, is_deleted) 唯一键约束;
|
||||
-- user_id 存 SystemTenantUser.uid(不是 JWT 里的 identity_id)。
|
||||
-- 2. 删除为软删除:is_deleted=0 表示未删除;删除时写入记录 ID 作为删除批次标记,
|
||||
-- 使唯一键在「删除后同一天重新填写」时不与历史软删记录冲突。
|
||||
-- 评论同步软删除(is_deleted=1)。
|
||||
-- 3. 同一天允许先存草稿(status=0)后提交(status=1)。
|
||||
-- 4. 不显式指定 COLLATE,沿用数据库默认排序规则,避免与其他表
|
||||
-- JOIN 字符串时出现 Illegal mix of collations。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 工作日报主表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_daily_report` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -45,8 +25,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_daily_report` (
|
||||
KEY `idx_tid_org_date` (`tid`, `org_id`, `report_date`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-工作日报';
|
||||
|
||||
-- ---------------- 2. 日报评论表 ----------------
|
||||
-- reply_to_id 指向同表评论ID,用于两级回复(0 表示直接评论日报)。
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_daily_report_comment` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
|
||||
@@ -1,20 +1,3 @@
|
||||
-- =============================================================
|
||||
-- OA 工作日报 —— 修改痕迹表
|
||||
--
|
||||
-- 对应代码:
|
||||
-- models/oa_daily_report.go(OaDailyReportHistory)
|
||||
-- services/dailyreport/report.go(Withdraw / Save / GetDetail)
|
||||
-- controllers/backend_oa_dailyreport.go(后台 PC 端)
|
||||
-- controllers/app_oa_dailyreport.go(小程序端)
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 日报提交后锁定(status=1),不允许直接修改;
|
||||
-- 需要修改时必须先「撤销提交」退回草稿(status=0),改完再重新提交。
|
||||
-- 2. 每次撤销提交写入一条 action=1 的痕迹,保存本次提交时的内容快照;
|
||||
-- 撤销后重新提交写入一条 action=2 的痕迹,保存新版本内容快照。
|
||||
-- 3. 痕迹只增不改:日报删除后痕迹保留(report_id 仍可追溯),不做软删除。
|
||||
-- 4. 不显式指定 COLLATE,沿用数据库默认排序规则,避免 JOIN 时排序规则冲突。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
@@ -1,22 +1,3 @@
|
||||
-- =============================================================
|
||||
-- OA 日程管理 —— 中国法定节假日/调休日表
|
||||
--
|
||||
-- 表结构变更一律以 SQL 文件形式放在 docs/sql/ 下由人工执行,
|
||||
-- 代码中不做自动建表。本脚本仅新建表,不改动任何既有数据。
|
||||
--
|
||||
-- 数据说明:
|
||||
-- 本表全局共享(不按租户隔离),只存两类无法用"星期几"推算出来的日期:
|
||||
-- type = 1 休假日(法定节假日放假,含调休连休的日子)
|
||||
-- type = 0 工作日(调休上班,即周末补班)
|
||||
-- 普通周六/周日不入库,由前端按星期直接判定。
|
||||
--
|
||||
-- 表本身可以为空:后端接口在查不到数据时会调用外网接口拉取并写入本表,
|
||||
-- 外网不可用时回落到代码内置的 2024-2026 年节假日数据(go/pkg/holiday/fallback.go),
|
||||
-- 因此不执行本脚本之外的任何数据预置也能正常使用。
|
||||
--
|
||||
-- 注意:不显式指定 COLLATE,沿用数据库默认排序规则,避免与既有表在
|
||||
-- JOIN 比较字符串时报 Illegal mix of collations。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
@@ -1,34 +1,6 @@
|
||||
-- =============================================================
|
||||
-- OA 职级管理 —— 表结构
|
||||
--
|
||||
-- 对应代码:
|
||||
-- models/backend_job_rank.go 职级模型
|
||||
-- controllers/backend_job_rank.go 职级 CRUD 接口
|
||||
--
|
||||
-- 职级(Job Rank)用于定义「职位等级」:
|
||||
-- · 每个部门可以各设一套职级阶梯。department_id 指向
|
||||
-- yz_backend_organization.id;department_id = 0 表示
|
||||
-- 全公司通用职级,任何部门都能选用。
|
||||
-- · level_no 是等级序号(数字越大职级越高),用于排序与
|
||||
-- 「取不超过某职级的最高一级」这类计算。
|
||||
-- · salary_min / salary_max 是该职级的标准薪资区间,
|
||||
-- 薪酬方案选定职级后据此带出参考薪资。
|
||||
-- · default_role_id 是为「职级 → 角色权限绑定」预留的字段,
|
||||
-- 本期不启用,后端不做任何自动授权,等权限方案确定后单独做。
|
||||
--
|
||||
-- 使用链路:
|
||||
-- 员工(yz_backend_employee) → 职位(yz_backend_position.rank_id)
|
||||
-- → 职级(yz_backend_job_rank)
|
||||
-- 薪酬方案(yz_backend_oa_compensation_schemes.rank_id) → 职级
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) 本脚本:建表 + 给职位表 / 薪酬方案表补 rank_id 列
|
||||
-- 2) oa_job_rank_menus.sql:注册「OA → 基础设置 → 职级管理」菜单并授权角色
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 职级表 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_job_rank` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'ID',
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -51,13 +23,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_job_rank` (
|
||||
KEY `idx_tid_code` (`tid`, `rank_code`) USING BTREE
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='职级表';
|
||||
|
||||
-- =============================================================
|
||||
-- 给既有表补 rank_id 列
|
||||
-- MySQL 不支持 ADD COLUMN IF NOT EXISTS,先查 information_schema 再动态执行,
|
||||
-- 保证脚本可重复执行。
|
||||
-- =============================================================
|
||||
|
||||
-- ---------- yz_backend_position(职位挂职级) ----------
|
||||
SET @tbl := 'yz_backend_position';
|
||||
SET @col := 'rank_id';
|
||||
SET @exists := (
|
||||
@@ -72,7 +37,6 @@ SET @sql := IF(@exists = 0,
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- ---------- yz_backend_oa_compensation_schemes(薪酬方案带职级) ----------
|
||||
SET @tbl := 'yz_backend_oa_compensation_schemes';
|
||||
SET @col := 'rank_id';
|
||||
SET @exists := (
|
||||
@@ -87,7 +51,6 @@ SET @sql := IF(@exists = 0,
|
||||
);
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- ---------------- 校验 ----------------
|
||||
SHOW CREATE TABLE `yz_backend_job_rank`;
|
||||
|
||||
SELECT TABLE_NAME, COLUMN_NAME, COLUMN_TYPE, COLUMN_COMMENT
|
||||
|
||||
@@ -1,32 +1,6 @@
|
||||
-- =============================================================
|
||||
-- OA 工作排班 —— 表结构
|
||||
--
|
||||
-- 对应代码:
|
||||
-- models/oa_scheduling.go
|
||||
-- controllers/backend_oa_scheduling.go (班次管理)
|
||||
-- controllers/backend_oa_scheduling_scope.go (组织/员工范围展开)
|
||||
-- controllers/backend_oa_scheduling_plan.go (排班方案与发布)
|
||||
-- controllers/backend_oa_scheduling_board.go (看板、临时调配、变更记录)
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) 本脚本:创建 4 张排班表
|
||||
-- 2) oa_scheduling_menus.sql:注册「OA → 排班考勤 → 工作排班」菜单并授权角色
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 排班对象直接复用租户组织架构(yz_backend_organization)与员工表
|
||||
-- (yz_backend_employee),不另建“小组”表:公司、部门、小组都是组织
|
||||
-- 树上的节点,方案通过 scope_type + org_id + include_child 决定范围。
|
||||
-- 2. 方案(plan)只保存规则;发布后展开成明细(entry),一人一天一条。
|
||||
-- 看板与临时调配只操作明细,方案可重复发布(可选覆盖)。
|
||||
-- 3. 明细软删除:is_deleted=0 表示有效,删除时写入记录 ID,
|
||||
-- 使唯一键 (tid, employee_id, schedule_date, is_deleted) 在删除后
|
||||
-- 同一天重新排班时不会与历史记录冲突。
|
||||
-- 4. 变更留痕(change)只记录人、日期与新旧班次,方便追溯临时调配。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 班次定义 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_shift` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -51,7 +25,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_shift` (
|
||||
KEY `idx_tid_deleted` (`tid`, `is_deleted`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-工作排班班次';
|
||||
|
||||
-- ---------------- 2. 排班方案 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_plan` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -85,7 +58,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_plan` (
|
||||
KEY `idx_tid_dates` (`tid`, `start_date`, `end_date`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-工作排班方案';
|
||||
|
||||
-- ---------------- 3. 排班明细 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_entry` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -120,7 +92,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_entry` (
|
||||
KEY `idx_tid_shift` (`tid`, `shift_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-工作排班明细';
|
||||
|
||||
-- ---------------- 4. 排班变更记录 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_change` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tid` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '租户ID',
|
||||
@@ -143,7 +114,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_oa_schedule_change` (
|
||||
KEY `idx_tid_entry` (`tid`, `entry_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='OA-工作排班变更记录';
|
||||
|
||||
-- ---------------- 校验 ----------------
|
||||
SELECT TABLE_NAME, TABLE_COMMENT
|
||||
FROM information_schema.TABLES
|
||||
WHERE TABLE_SCHEMA = DATABASE()
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
-- 平台 AI Playground 会话与消息表
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_ai_chat_session` (
|
||||
`id` bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
`title` varchar(100) NOT NULL DEFAULT '' COMMENT '会话标题(首条用户消息摘要)',
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
-- 平台级 AI 服务商配置(platform「AI管理」页签:DeepSeek / 豆包 / Codex 等接入)
|
||||
-- 人工执行;表数据驱动,前端按 provider_type 区分不同服务商 tab
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_ai_provider` (
|
||||
`id` bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
|
||||
@@ -1,23 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 平台端排班模板(全局预制模板 + 自定义模板)
|
||||
--
|
||||
-- 执行顺序:
|
||||
-- 1) 本脚本:创建 2 张模板表并写入 6 个系统预置模板
|
||||
-- 2) alter_oa_schedule_plan_template.sql:租户排班方案增加模板/周期字段
|
||||
-- 3) platform_sched_template_menu.sql:注册平台端「排班模板」菜单
|
||||
-- 4) create_oa_scheduling.sql / oa_scheduling_menus.sql(若尚未执行)
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. 模板是全局数据(不按租户隔离),只有平台端可维护;
|
||||
-- 系统预置模板(is_system=1)由平台锁定:不可编辑、不可删除、不可停用。
|
||||
-- 2. 租户端只能「调用」模板:调用时把模板规则快照到自己的排班方案
|
||||
-- (yz_backend_oa_schedule_plan.pattern),之后在租户端随意修改,
|
||||
-- 模板本身的后续调整不会再影响已保存的方案。
|
||||
-- 3. align_mode:1=按自然周(双休/单休/大小周) 2=从开始日滚动(三班倒/做一休一)
|
||||
-- 3=按自然月(月休,按月计算休息日)
|
||||
-- 4. day_index 表示周期内第几天,从 0 开始;按自然周时 0=周一、6=周日。
|
||||
-- 5. 本脚本不使用会话变量 / PREPARE,可整段执行也可逐条执行,重复执行安全。
|
||||
-- ============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_sched_tpl` (
|
||||
`id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT '主键',
|
||||
@@ -60,11 +40,6 @@ CREATE TABLE IF NOT EXISTS `yz_platform_sched_tpl_day` (
|
||||
UNIQUE KEY `uk_tpl_day` (`template_id`,`day_index`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='平台端排班模板-周期每日规则';
|
||||
|
||||
-- ============================================================
|
||||
-- 系统预置模板(6 个)
|
||||
-- ============================================================
|
||||
|
||||
-- 1. 双休:周一至周五上班,周六日休息
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'double_weekend', '双休', 1, 1, 7, 0, 0, 0, '周一至周五上班 09:00-18:00,周六日休息', 1, 1, 10, 'system'
|
||||
@@ -89,7 +64,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- 2. 单休:周一至周六上班,周日休息
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'single_weekend', '单休', 2, 1, 7, 0, 0, 0, '周一至周六上班 09:00-18:00,周日休息', 1, 1, 20, 'system'
|
||||
@@ -114,7 +88,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- 3. 大小周:第 1 周双休,第 2 周单休(周六上班),14 天一个周期
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'big_small_week', '大小周', 3, 1, 14, 0, 0, 0, '第 1 周双休、第 2 周单休(周六上班),14 天循环', 1, 1, 30, 'system'
|
||||
@@ -146,7 +119,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- 4. 月休 4 天:每月固定休 4 天,优先安排在周日(周末不足时从月末补齐)
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'month_4_rest', '月休 4 天', 4, 3, 0, 0, 4, 7, '每月固定休 4 天,优先安排周日,遇 5 个周日只休前 4 个', 1, 1, 40, 'system'
|
||||
@@ -165,7 +137,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- 5. 三班倒:早班 -> 中班 -> 夜班,各 1 天循环
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'three_shift', '三班倒', 5, 2, 3, 0, 0, 0, '早班 08:00-16:00 → 中班 16:00-24:00 → 夜班 00:00-08:00,3 天循环', 1, 1, 50, 'system'
|
||||
@@ -186,7 +157,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- 6. 做一休一:上 1 天休 1 天
|
||||
INSERT INTO yz_platform_sched_tpl
|
||||
(code, name, template_type, align_mode, cycle_days, week_offset, month_rest_days, month_rest_weekday, summary, is_system, status, sort, creater)
|
||||
SELECT 'work_one_rest_one', '做一休一', 6, 2, 2, 0, 0, 0, '上 1 天休 1 天循环(09:00-18:00)', 1, 1, 60, 'system'
|
||||
@@ -206,9 +176,6 @@ WHERE NOT EXISTS (
|
||||
WHERE x.template_id = tpl.id AND x.day_index = d.idx
|
||||
);
|
||||
|
||||
-- ============================================================
|
||||
-- 结果校验:6 行,day_count 分别为 7 / 7 / 14 / 1 / 3 / 2
|
||||
-- ============================================================
|
||||
SELECT t.id, t.code, t.name, t.template_type, t.align_mode, t.cycle_days,
|
||||
t.month_rest_days, t.month_rest_weekday, t.is_system, t.status, t.sort,
|
||||
COUNT(d.id) AS day_count
|
||||
|
||||
@@ -1,14 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 平台官网 - 站点公告
|
||||
-- 表:yz_platform_website_notice
|
||||
--
|
||||
-- 用途:平台端「官网管理 → 内容管理 → 站点公告」维护官网的通知 / 活动 /
|
||||
-- 系统维护类公告;前台经 GET /site/notices 读取(仅返回「已发布」
|
||||
-- 且处于有效期内的公告)。
|
||||
--
|
||||
-- 执行方式:人工在数据库执行(代码中不做任何自动建表 / 补列)。
|
||||
-- 说明:下方 DDL 幂等,可重复执行。
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_website_notice` (
|
||||
`id` bigint UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID',
|
||||
@@ -35,25 +24,12 @@ CREATE TABLE IF NOT EXISTS `yz_platform_website_notice` (
|
||||
KEY `idx_publish_time` (`publish_time`)
|
||||
) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COMMENT = '平台官网-站点公告';
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 平台菜单:把「站点公告」挂到「官网管理 → 内容管理」下
|
||||
--
|
||||
-- 菜单数据统一维护在 yz_system_menu(平台端 cid=1 的角色可见)。
|
||||
-- 父级不用写死自增ID,按现有「内容管理」的子菜单反查,可在任意环境重复执行。
|
||||
-- 若本次不需要自动挂菜单,可只执行上面的建表语句,手动在
|
||||
-- 「系统管理 → 菜单管理」里添加:路径 /website/content/notice,
|
||||
-- 组件 /website/content/notice/index.vue
|
||||
-- =============================================================
|
||||
|
||||
-- 父级定位一:取现有「内容管理」子菜单(文章管理)的 pid
|
||||
SET @notice_pid := (
|
||||
SELECT `pid` FROM `yz_system_menu`
|
||||
WHERE `delete_time` IS NULL AND `component_path` LIKE '/website/content/%'
|
||||
ORDER BY `id` ASC LIMIT 1
|
||||
);
|
||||
|
||||
-- 父级定位二:兜底按「内容管理」的路径或名称查
|
||||
SET @notice_pid := IFNULL(@notice_pid, (
|
||||
SELECT `id` FROM `yz_system_menu`
|
||||
WHERE `delete_time` IS NULL
|
||||
@@ -61,7 +37,6 @@ SET @notice_pid := IFNULL(@notice_pid, (
|
||||
ORDER BY `id` ASC LIMIT 1
|
||||
));
|
||||
|
||||
-- 已存在同路径菜单时跳过,避免重复插入
|
||||
INSERT INTO `yz_system_menu`
|
||||
(`pid`, `title`, `path`, `component_path`, `icon`, `sort`, `status`, `is_visible`, `views`, `type`, `creater`, `remark`, `create_time`)
|
||||
SELECT
|
||||
@@ -77,10 +52,6 @@ WHERE @notice_pid IS NOT NULL
|
||||
) AS `exist`
|
||||
);
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 可选:一条示例公告,便于前台联调(不需要可整段跳过)
|
||||
-- =============================================================
|
||||
INSERT INTO `yz_platform_website_notice`
|
||||
(`title`, `summary`, `content`, `type`, `is_popup`, `top`, `sort`, `status`, `publish_time`)
|
||||
VALUES
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
-- 微信公众号一次性登录令牌(未认证公众号无法使用网页授权,
|
||||
-- 用户在公众号发送「登录」→ 回复一次性链接 → 前端用令牌换取正式登录态)
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_wechat_mp_login_token` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`token` VARCHAR(64) NOT NULL COMMENT '一次性登录令牌',
|
||||
|
||||
@@ -1,6 +1,3 @@
|
||||
-- 微信公众号扫码登录会话(未认证公众号无带参二维码,用「公众号二维码 + 6 位登录码」替代:
|
||||
-- PC 端展示二维码与登录码 → 用户扫码进入公众号会话发送登录码 → 服务号回复确认登录链接 →
|
||||
-- 点击链接(/mp-login 兑换)后 PC 端轮询本表拿到确认状态并签发令牌自动登录)
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_wechat_mp_scan_login` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`scene` VARCHAR(64) NOT NULL COMMENT 'PC 登录会话标识',
|
||||
|
||||
@@ -1,26 +1,10 @@
|
||||
-- ============================================================
|
||||
-- 租户附件空间(配额 + 单独计费的存储套餐)
|
||||
--
|
||||
-- 1) yz_system_tenant 增加基础额度 storage_quota_mb(默认 500MB)
|
||||
-- 2) 存储套餐表 yz_system_tenant_storage_package(平台自由维护)
|
||||
-- 3) 存储订单表 yz_system_tenant_storage_order(接支付,支付成功自动开通)
|
||||
-- 4) 菜单:租户端「存储空间」、平台端「存储套餐」
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. ALTER 语句不可重复执行;若报「Duplicate column name」说明已加过,可忽略。
|
||||
-- 2. CREATE TABLE 使用 IF NOT EXISTS,可重复执行。
|
||||
-- 3. 菜单按 path 判重,可重复执行。
|
||||
-- ============================================================
|
||||
|
||||
-- ---------- 1. 租户基础额度 ----------
|
||||
ALTER TABLE yz_system_tenant
|
||||
ADD COLUMN storage_quota_mb INT NOT NULL DEFAULT 500
|
||||
COMMENT '基础附件空间MB(不含已购存储套餐;实际可用=max(本值, 生效套餐容量))';
|
||||
|
||||
-- 存量租户初始化为 500MB(新增列默认值即可,这里兜底一次)
|
||||
UPDATE yz_system_tenant SET storage_quota_mb = 500 WHERE storage_quota_mb IS NULL OR storage_quota_mb = 0;
|
||||
|
||||
-- ---------- 2. 存储套餐 ----------
|
||||
CREATE TABLE IF NOT EXISTS yz_system_tenant_storage_package (
|
||||
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
name VARCHAR(64) NOT NULL DEFAULT '' COMMENT '套餐名称,如 5GB / 20GB',
|
||||
@@ -38,7 +22,6 @@ CREATE TABLE IF NOT EXISTS yz_system_tenant_storage_package (
|
||||
KEY idx_status_sort (status, sort)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='租户附件空间套餐';
|
||||
|
||||
-- ---------- 3. 存储订单 ----------
|
||||
CREATE TABLE IF NOT EXISTS yz_system_tenant_storage_order (
|
||||
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
order_no VARCHAR(64) NOT NULL COMMENT '业务订单号(支付 out_trade_no)',
|
||||
@@ -63,12 +46,8 @@ CREATE TABLE IF NOT EXISTS yz_system_tenant_storage_order (
|
||||
KEY idx_tid_end (tid, end_time)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='租户附件空间订单';
|
||||
|
||||
-- 文件表补索引:按租户统计已用空间(SUM(size))
|
||||
-- 已存在同名索引时报 Duplicate key name,可忽略。
|
||||
ALTER TABLE yz_system_files ADD INDEX idx_tid_source_size (tid, source, size);
|
||||
|
||||
-- ---------- 4. 菜单 ----------
|
||||
-- 4.1 租户端「存储空间」:挂到租户端「基础设置」下
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT
|
||||
@@ -89,7 +68,6 @@ FROM DUAL
|
||||
WHERE NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL) b)
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/storage' AND delete_time IS NULL) e);
|
||||
|
||||
-- 4.2 平台端「存储套餐」:挂到平台端「基础设置」下
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT
|
||||
@@ -110,7 +88,6 @@ FROM DUAL
|
||||
WHERE NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL) b)
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/storagePackage' AND delete_time IS NULL) e);
|
||||
|
||||
-- ---------- 5. 预置套餐(价格请按实际调整;同 code 重复执行不会插入) ----------
|
||||
INSERT INTO yz_system_tenant_storage_package
|
||||
(name, code, capacity_mb, price, duration_days, sort, status, remark)
|
||||
SELECT '5GB', 'storage_5g', 5120, 100.00, 365, 1, 1, '5GB / 年'
|
||||
|
||||
@@ -1,25 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 移动端「常用功能」自定义入口
|
||||
--
|
||||
-- 说明:uniapp 子系统首页「常用功能」宫格由用户自行挑选要展示的功能,
|
||||
-- 末位固定为「+」用于打开选择器增删。每个租户下的每个用户维护一份有序
|
||||
-- 的功能菜单 ID 列表,存于本表。
|
||||
--
|
||||
-- 关联代码:
|
||||
-- 模型 go/models/uniapp_user_quick_menu.go (UniappUserQuickMenu)
|
||||
-- 接口 GET /app/home → data.quick_menu_ids(读取)
|
||||
-- POST /app/quick-menus → 保存(全量覆盖)
|
||||
--
|
||||
-- 约定:
|
||||
-- - yz_uniapp_ 前缀代表移动端(uniapp)专属数据表
|
||||
-- - tid 租户 ID(对应 JWT claims.TenantId)
|
||||
-- - uid 用户身份 ID(对应 JWT claims.UserID,与业务表 user_id 同源)
|
||||
-- - menu_ids JSON 数组字符串,元素为 yz_system_menu.id,顺序即展示顺序
|
||||
-- 例:[81,101,102,113,116]
|
||||
-- - 一个 (tid, uid) 仅一条记录,保存走 upsert,唯一键保证。
|
||||
--
|
||||
-- 本表由人工执行建表,代码不做自动建表(见 models/init.go 约定)。
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_uniapp_user_quick_menu` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键',
|
||||
|
||||
@@ -1,11 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 微信小程序多应用配置(yz_platform_wechat_mini_app)
|
||||
-- 支持配置多个小程序:认证端登录时按客户端传入 appid 精确匹配,
|
||||
-- 未传 appid 时回退第一条启用记录。
|
||||
-- AppSecret 以 AES-256-GCM 加密存储(复用 wechatmp 的密钥)。
|
||||
-- 幂等脚本:重复执行不会产生重复数据。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < create_wechat_mini_app.sql
|
||||
-- ============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS yz_platform_wechat_mini_app (
|
||||
id bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
@@ -23,7 +15,6 @@ CREATE TABLE IF NOT EXISTS yz_platform_wechat_mini_app (
|
||||
UNIQUE KEY uk_mini_app_appid (app_id)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='微信小程序多应用配置';
|
||||
|
||||
-- 迁移旧单行配置(yz_platform_wechat_mini_config)到新表;已存在同 appid 时跳过
|
||||
INSERT INTO yz_platform_wechat_mini_app (name, app_id, app_secret, enabled, auto_bind, remark)
|
||||
SELECT COALESCE(NULLIF(c.remark, ''), '默认小程序'), c.app_id, c.app_secret, c.enabled, c.auto_bind, c.remark
|
||||
FROM yz_platform_wechat_mini_config c
|
||||
@@ -32,7 +23,6 @@ WHERE c.app_id <> ''
|
||||
SELECT 1 FROM (SELECT 1 FROM yz_platform_wechat_mini_app x WHERE x.app_id = c.app_id) t
|
||||
);
|
||||
|
||||
-- 结果校验
|
||||
SELECT id, name, app_id, enabled, auto_bind, remark, qrcode_url
|
||||
FROM yz_platform_wechat_mini_app
|
||||
WHERE delete_time IS NULL;
|
||||
@@ -1,16 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 微信小程序配置(统一认证 · 小程序一键登录)
|
||||
--
|
||||
-- 小程序与公众号是两套独立应用,AppID / AppSecret 不可混用,
|
||||
-- 因此单独建表。app_secret 以 AES-256-GCM 密文存储(YZW1: 前缀)。
|
||||
--
|
||||
-- 关联链路:
|
||||
-- uniapp 小程序 → wx.login / getPhoneNumber
|
||||
-- → POST /auth/wechat/miniapp/login
|
||||
-- → jscode2session 换 openid → 按手机号定位 yz_auth_identity
|
||||
-- → 写入 yz_auth_identity_third(provider='wechat_mini')
|
||||
-- → 复用统一认证的会话与令牌(yz_auth_session / yz_auth_refresh_token)
|
||||
-- =============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `yz_platform_wechat_mini_config` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键',
|
||||
@@ -24,19 +11,9 @@ CREATE TABLE IF NOT EXISTS `yz_platform_wechat_mini_config` (
|
||||
PRIMARY KEY (`id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='微信小程序配置';
|
||||
|
||||
-- -------------------------------------------------------------
|
||||
-- 接入应用:微信小程序(app_type=4)
|
||||
-- 小程序不走浏览器跳转,只用 POST /auth/wechat/miniapp/login 换令牌,
|
||||
-- 因此无需登记 redirect_uris。
|
||||
-- -------------------------------------------------------------
|
||||
INSERT INTO `yz_auth_client`
|
||||
(`client_id`, `app_code`, `name`, `app_type`, `grant_types`, `scope`, `access_ttl`, `refresh_ttl`, `realm`)
|
||||
VALUES
|
||||
('yz-miniapp', 'miniapp', '微信小程序', 4, 'authorization_code,refresh_token', 'openid,profile,tenant', 1800, 2592000, 'tenant')
|
||||
ON DUPLICATE KEY UPDATE `name` = VALUES(`name`);
|
||||
|
||||
-- -------------------------------------------------------------
|
||||
-- 第三方身份源:允许 yz_auth_identity_third.provider 出现 'wechat_mini'
|
||||
-- (表结构本身为 varchar,无需 DDL;此处仅作说明)
|
||||
-- provider = 'wechat_mini',open_id = 小程序 openid,union_id = 小程序 unionid
|
||||
-- -------------------------------------------------------------
|
||||
@@ -1,15 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 小程序订阅消息:模板配置 + 授权记录
|
||||
-- yz_platform_wechat_mini_template 订阅消息模板(按小程序 + 场景码)
|
||||
-- yz_platform_wechat_mini_subscribe 用户授权记录(一次性订阅的剩余发送次数)
|
||||
--
|
||||
-- 模板 ID 需要在小程序后台「功能 → 订阅消息 → 公共模板库」选用后填入平台端。
|
||||
-- fields 为 JSON:微信模板字段键 → 语义变量名,例如
|
||||
-- {"thing1":"title","phrase2":"content","time3":"time"}
|
||||
--
|
||||
-- 幂等脚本:重复执行不会产生重复数据。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < create_wechat_mini_template.sql
|
||||
-- ============================================================
|
||||
|
||||
CREATE TABLE IF NOT EXISTS yz_platform_wechat_mini_template (
|
||||
id bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
@@ -40,6 +28,5 @@ CREATE TABLE IF NOT EXISTS yz_platform_wechat_mini_subscribe (
|
||||
UNIQUE KEY uk_mini_sub_identity_tpl (identity_id, app_id, template_id)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='小程序订阅消息授权记录';
|
||||
|
||||
-- 结果校验
|
||||
SELECT id, app_id, code, template_id, title, page, enabled FROM yz_platform_wechat_mini_template
|
||||
WHERE delete_time IS NULL;
|
||||
@@ -1,30 +1,6 @@
|
||||
-- =============================================================
|
||||
-- 进销存(ERP)—— 交易层数据表
|
||||
--
|
||||
-- 对应模型:go/models/erp_inventory.go
|
||||
--
|
||||
-- 设计要点:
|
||||
-- 1. 库存流水表 yz_backend_erp_stock_ledger 是核心:所有出入库动作
|
||||
-- 审核生效时写入一条不可篡改的流水,由流水驱动库存结存
|
||||
-- yz_backend_erp_stock(qty + 移动加权成本),不直接改库存数字。
|
||||
-- 2. 单据统一建模:yz_backend_erp_document(主表)+ _item(明细),
|
||||
-- doc_type 覆盖 采购订单/入库/退货、销售订单/出库/退货、
|
||||
-- 其他出入库、调拨、盘点 十类单据,一套单据引擎驱动全部流转。
|
||||
-- 单据特有字段:book_qty(盘点账面)、to_warehouse_id(调拨)、
|
||||
-- ref_doc_id/ref_item_id(退货溯源、入库关联订单)。
|
||||
-- 3. 业财一体:出库/入库单生效时生成往来账 yz_backend_erp_partner_bill
|
||||
-- (应收/应付),收付款单 yz_backend_erp_fund_bill 通过
|
||||
-- yz_backend_erp_fund_settle 按单核销。
|
||||
-- 4. 状态机:0草稿 1审批中 2已生效 3已驳回 4已作废;
|
||||
-- 仅「已生效」产生库存流水与往来账;草稿/驳回/审批中可作废。
|
||||
--
|
||||
-- 注意:不显式指定 COLLATE,沿用数据库默认排序规则,避免与既有表
|
||||
-- (utf8mb4_0900_ai_ci)在 JOIN 比较字符串时报 Illegal mix of collations。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
-- ---------------- 1. 商品分类(树形) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_product_category` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -40,7 +16,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_product_category` (
|
||||
KEY `idx_tenant` (`tenant_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-商品分类';
|
||||
|
||||
-- ---------------- 2. 商品档案 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_product` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -79,7 +54,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_product` (
|
||||
KEY `idx_barcode` (`barcode`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-商品档案';
|
||||
|
||||
-- ---------------- 3. 仓库 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_warehouse` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -98,7 +72,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_warehouse` (
|
||||
KEY `idx_tenant` (`tenant_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-仓库档案';
|
||||
|
||||
-- ---------------- 4. 库存结存(由流水驱动) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_stock` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -113,7 +86,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_stock` (
|
||||
KEY `idx_tenant_product` (`tenant_id`,`product_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-库存结存';
|
||||
|
||||
-- ---------------- 5. 库存流水(核心·只增不改不删) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_stock_ledger` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -142,7 +114,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_stock_ledger` (
|
||||
KEY `idx_create_time` (`tenant_id`,`create_time`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-库存流水(不可篡改)';
|
||||
|
||||
-- ---------------- 6. 单据主表(十类单据统一建模) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_document` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -177,7 +148,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_document` (
|
||||
KEY `idx_biz_date` (`tenant_id`,`biz_date`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-业务单据主表';
|
||||
|
||||
-- ---------------- 7. 单据明细 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_document_item` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`doc_id` BIGINT UNSIGNED NOT NULL DEFAULT 0 COMMENT '主表ID',
|
||||
@@ -203,7 +173,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_document_item` (
|
||||
KEY `idx_tenant_product` (`tenant_id`,`product_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-业务单据明细';
|
||||
|
||||
-- ---------------- 8. 往来账(应收/应付) ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_partner_bill` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -227,7 +196,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_partner_bill` (
|
||||
KEY `idx_doc` (`tenant_id`,`source_doc_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-往来账(应收/应付)';
|
||||
|
||||
-- ---------------- 9. 收付款单 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_fund_bill` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT '租户ID',
|
||||
@@ -253,7 +221,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_fund_bill` (
|
||||
KEY `idx_tenant_type` (`tenant_id`,`fund_type`,`status`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-收付款单';
|
||||
|
||||
-- ---------------- 10. 收付款核销明细 ----------------
|
||||
CREATE TABLE IF NOT EXISTS `yz_backend_erp_fund_settle` (
|
||||
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
|
||||
`tenant_id` VARCHAR(64) NOT NULL DEFAULT '',
|
||||
@@ -267,9 +234,6 @@ CREATE TABLE IF NOT EXISTS `yz_backend_erp_fund_settle` (
|
||||
KEY `idx_bill` (`partner_bill_id`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='ERP-收付款核销明细';
|
||||
|
||||
-- ---------------- 11. 客户/供应商信用字段(幂等增列) ----------------
|
||||
-- MySQL 不支持 ADD COLUMN IF NOT EXISTS,用 INFORMATION_SCHEMA 判重 + PREPARE 动态执行。
|
||||
|
||||
SET @has_credit := (SELECT COUNT(*) FROM information_schema.columns
|
||||
WHERE table_schema=DATABASE() AND table_name='yz_backend_erp_customer' AND column_name='credit_limit');
|
||||
SET @sql := IF(@has_credit=0,
|
||||
@@ -284,6 +248,5 @@ SET @sql := IF(@has_spay=0,
|
||||
'SELECT ''yz_backend_erp_supplier.payment_days already exists''');
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- ---------------- 结果校验 ----------------
|
||||
SELECT TABLE_NAME, TABLE_COMMENT FROM information_schema.tables
|
||||
WHERE table_schema=DATABASE() AND TABLE_NAME LIKE 'yz_backend_erp_%' ORDER BY TABLE_NAME;
|
||||
@@ -1,26 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 进销存(erp)—— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> --default-character-set=utf8mb4 < erp_menus.sql
|
||||
-- ============================================================
|
||||
-- 目标结构(「大类」= 模块根下一层目录,会作为移动端功能页的分组标题;
|
||||
-- 「小类」= 叶子菜单,渲染为功能卡片):
|
||||
-- 工作台(目录)-> 工作台(仪表盘 /apps/erp/dashboard)/ 审批列表(/apps/erp/workbench/approval)
|
||||
-- 基础资料 -> 商品 / 供应商 / 客户 / 仓库
|
||||
-- 采购管理 -> 采购订单 / 采购入库 / 采购退货
|
||||
-- 销售管理 -> 销售订单 / 销售出库 / 销售退货
|
||||
-- 库存管理 -> 入库 / 出库 / 调拨 / 盘点 / 库存查询 / 库存预警
|
||||
-- 财务管理 -> 应收 / 应付 / 收付款
|
||||
-- 报表中心 -> 报表中心
|
||||
-- 系统管理 -> 系统管理 / 账套管理(账套列表)/ 基础设置
|
||||
--
|
||||
-- 字段说明:
|
||||
-- type 1=目录(大类),2=页面(小类)
|
||||
-- views '[2]' 租户端:Web 租户后台与移动端共用同一份菜单
|
||||
-- platforms 留 NULL:展示端继承 erp 模块配置
|
||||
-- component_path 由「3.1 页面文件登记」统一写入;未登记的菜单 Web 端为空白页,
|
||||
-- 移动端落到「功能开发中」占位页
|
||||
-- icon 完整 Font Awesome 类名;移动端必须落在 uniapp/utils/fa-icons.js 白名单内才显示
|
||||
|
||||
SET @erp_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -28,7 +5,6 @@ SET @erp_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 1. 八个大类(目录) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @erp_id, '工作台', '/apps/erp/workbench', NULL, 'fa-solid fa-gauge', 1, 1, 1, '[2]', 1, 'system', '进销存大类:工作台'
|
||||
@@ -36,7 +12,6 @@ FROM DUAL
|
||||
WHERE @erp_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/erp/workbench' AND delete_time IS NULL) x);
|
||||
|
||||
-- 工作台必须是目录:历史数据里可能被建成了页面,统一纠正,目录内才放工作台/审批列表两个页面
|
||||
UPDATE yz_system_menu
|
||||
SET type = 1, component_path = NULL, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/workbench'
|
||||
@@ -91,18 +66,14 @@ FROM DUAL
|
||||
WHERE @erp_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/erp/system' AND delete_time IS NULL) x);
|
||||
|
||||
-- 取回八个大类的ID,供小类挂载
|
||||
SET @erp_workbench := (SELECT id FROM yz_system_menu WHERE path = '/apps/erp/workbench' AND delete_time IS NULL LIMIT 1);
|
||||
SET @erp_basic := (SELECT id FROM yz_system_menu WHERE path = '/apps/erp/basic' AND delete_time IS NULL LIMIT 1);
|
||||
SET @erp_system := (SELECT id FROM yz_system_menu WHERE path = '/apps/erp/system' AND delete_time IS NULL LIMIT 1);
|
||||
|
||||
-- ---------- 2. 已有菜单迁入新树(避免同一功能出现两份) ----------
|
||||
-- 仪表盘 -> 工作台目录内的「工作台」页面;路由与页面文件不变
|
||||
UPDATE yz_system_menu
|
||||
SET pid = @erp_workbench, title = '工作台', sort = 1, type = 2, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/dashboard' AND @erp_workbench IS NOT NULL;
|
||||
|
||||
-- 供应商列表 / 客户列表 -> 基础资料大类,去掉「列表」后缀;路由与页面文件不变
|
||||
UPDATE yz_system_menu
|
||||
SET pid = @erp_basic, title = '供应商', sort = 2, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/suppliers' AND @erp_basic IS NOT NULL;
|
||||
@@ -111,7 +82,6 @@ UPDATE yz_system_menu
|
||||
SET pid = @erp_basic, title = '客户', sort = 3, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/customers' AND @erp_basic IS NOT NULL;
|
||||
|
||||
-- 账套管理 / 基础设置 -> 系统管理大类
|
||||
UPDATE yz_system_menu
|
||||
SET pid = @erp_system, sort = 2, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND pid = @erp_id AND title = '账套管理' AND @erp_system IS NOT NULL;
|
||||
@@ -120,7 +90,6 @@ UPDATE yz_system_menu
|
||||
SET pid = @erp_system, sort = 3, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND pid = @erp_id AND title = '基础设置' AND @erp_system IS NOT NULL;
|
||||
|
||||
-- ---------- 3. 新增小类(页面) ----------
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_erp_leaf;
|
||||
CREATE TEMPORARY TABLE tmp_erp_leaf (
|
||||
parent_path VARCHAR(200) NOT NULL,
|
||||
@@ -165,9 +134,6 @@ WHERE e.id IS NULL;
|
||||
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_erp_leaf;
|
||||
|
||||
-- ---------- 3.1 页面文件登记 ----------
|
||||
-- 前端 pathResolver 先按 component_path 精确匹配,命中不到才按文件名模糊兜底,
|
||||
-- 模糊兜底会把菜单渲染成另一个同名 index.vue,所以这里一律写从 src/views 起的完整路径。
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_erp_page;
|
||||
CREATE TEMPORARY TABLE tmp_erp_page (
|
||||
path VARCHAR(200) NOT NULL,
|
||||
@@ -204,18 +170,15 @@ JOIN tmp_erp_page t ON t.path = m.path
|
||||
SET m.component_path = t.component_path, m.update_time = NOW()
|
||||
WHERE m.delete_time IS NULL AND (m.component_path IS NULL OR m.component_path <> t.component_path);
|
||||
|
||||
-- 基础设置 历史上挂成目录(type=1)又没有子菜单,登记页面后按叶子菜单处理
|
||||
UPDATE yz_system_menu SET type = 2, update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/ProgramManagement' AND type = 1;
|
||||
|
||||
-- 菜单行还没建(上一节未生效)时这里会列出来,执行后应重新跑一次本脚本
|
||||
SELECT t.path AS 未登记菜单 FROM tmp_erp_page t
|
||||
LEFT JOIN yz_system_menu m ON m.path = t.path AND m.delete_time IS NULL
|
||||
WHERE m.id IS NULL;
|
||||
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_erp_page;
|
||||
|
||||
-- 补图标:迁移过来的菜单原本没有图标,移动端会退化成兜底图标,这里只填空值、不覆盖已有配置
|
||||
UPDATE yz_system_menu SET icon = 'fa-solid fa-store', update_time = NOW()
|
||||
WHERE delete_time IS NULL AND path = '/apps/erp/suppliers' AND (icon IS NULL OR icon = '');
|
||||
|
||||
@@ -225,9 +188,6 @@ WHERE delete_time IS NULL AND path = '/apps/erp/customers' AND (icon IS NULL OR
|
||||
UPDATE yz_system_menu SET icon = 'fa-solid fa-book-bookmark', update_time = NOW()
|
||||
WHERE delete_time IS NULL AND pid = @erp_system AND title = '账套管理' AND (icon IS NULL OR icon = '');
|
||||
|
||||
-- ---------- 4. 清理被搬空的两级旧目录(供应商管理 / 客户管理) ----------
|
||||
-- 子菜单已迁走(供应商列表 / 客户列表),留着会变成空分组。
|
||||
-- 先取出「已无子菜单」的旧目录ID,再按ID软删除:MySQL 不允许在 UPDATE 的子查询里读同一张表。
|
||||
SET @erp_empty_dir := NULL;
|
||||
|
||||
SELECT GROUP_CONCAT(d.id) INTO @erp_empty_dir
|
||||
@@ -243,7 +203,6 @@ UPDATE yz_system_menu
|
||||
SET delete_time = NOW(), status = 0
|
||||
WHERE delete_time IS NULL AND FIND_IN_SET(id, IFNULL(@erp_empty_dir, ''));
|
||||
|
||||
-- ---------- 5. 结果校验(大类 + 其下小类) ----------
|
||||
SELECT d.sort AS 大类序号, d.title AS 大类, IFNULL(m.title, '(无)') AS 小类, m.sort AS 小类序号,
|
||||
m.path AS 路径, m.icon AS 图标, m.component_path AS 页面文件
|
||||
FROM yz_system_menu d
|
||||
|
||||
@@ -1,30 +1,4 @@
|
||||
-- =============================================================================
|
||||
-- 人员管理(yz_backend_employee) 与 用户管理(yz_system_tenant_user) 老数据对齐
|
||||
--
|
||||
-- 背景:员工表早期建的是「账号全局唯一」索引 uk_account(account),多租户后同一账号
|
||||
-- 在不同企业只能存在一份员工档案;再叠加历史手工录入的人员(如 hero001 这类旧账号),
|
||||
-- 导致「OA 设置 → 人员管理」与「基本设置 → 用户管理」两边数据对不上。
|
||||
--
|
||||
-- 处理内容:
|
||||
-- 1. 索引调整为 (tid, account) 唯一 ← 必须最先执行,否则第 3 步会撞全局唯一键
|
||||
-- 2. 员工 tid 为空/0:按唯一账号补 tid
|
||||
-- 3. 同一企业内「用户缺员工 + 存在同名无账号老员工」:把老员工账号改成用户账号
|
||||
-- (保留员工 ID,排班 / 日报 / 人事档案的历史引用不受影响)
|
||||
-- 4. 用户仍然没有员工:按用户资料补建员工记录(与「用户管理 → 同步员工」同规则)
|
||||
-- 5. 复核查询 + 仍需人工确认的清单
|
||||
--
|
||||
-- 反向缺口(「人员管理有、用户管理没有」)不在这里处理:补账号要先在统一认证建身份
|
||||
-- 并生成 argon2id 密码哈希,SQL 做不到,用 Go 工具:
|
||||
-- go run scripts/syncemployeeusers/main.go -tid <企业ID> -apply
|
||||
--
|
||||
-- 特性:可重复执行(幂等),第 2 次执行不会产生任何变更。
|
||||
-- 执行前请务必备份:mysqldump -u root -p go-platform > backup_$(date +%F).sql
|
||||
-- 执行后请重启 backend 服务:services/employee_sync.go 已改为按 (tid, account) 匹配员工。
|
||||
-- =============================================================================
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 0. 执行前预检(只看不改)
|
||||
-- -----------------------------------------------------------------------------
|
||||
SELECT '执行前:用户/员工数量' AS section;
|
||||
SELECT
|
||||
(SELECT COUNT(*) FROM yz_system_tenant_user WHERE delete_time IS NULL) AS user_rows,
|
||||
@@ -36,7 +10,6 @@ SELECT
|
||||
WHERE e.delete_time IS NULL AND e.tid = u.tid AND TRIM(e.account) = TRIM(u.account))
|
||||
) AS user_without_employee;
|
||||
|
||||
-- 若下面这条 > 0,需要先人工处理重复的 (tid, account),否则第 1 步加唯一索引会失败
|
||||
SELECT '重复的 (tid, account)' AS section;
|
||||
SELECT tid, TRIM(account) AS account, COUNT(*) AS cnt
|
||||
FROM yz_backend_employee
|
||||
@@ -44,10 +17,6 @@ WHERE delete_time IS NULL
|
||||
GROUP BY tid, TRIM(account)
|
||||
HAVING COUNT(*) > 1;
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 1. 索引:账号全局唯一 → 企业内唯一
|
||||
-- 关键:不先放开全局唯一,第 3 步把 hero001 改成 hero920103 会因另一企业已占用而失败
|
||||
-- -----------------------------------------------------------------------------
|
||||
SET @has_old := (SELECT COUNT(*) FROM information_schema.STATISTICS
|
||||
WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'yz_backend_employee'
|
||||
AND INDEX_NAME = 'uk_account');
|
||||
@@ -68,9 +37,6 @@ SET @sql := IF(@has_uk = 0,
|
||||
'DO 0');
|
||||
PREPARE stmt FROM @sql; EXECUTE stmt; DEALLOCATE PREPARE stmt;
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 2. 员工 tid 为空/0:按账号唯一匹配到企业用户后补 tid
|
||||
-- -----------------------------------------------------------------------------
|
||||
UPDATE yz_backend_employee e
|
||||
JOIN (
|
||||
SELECT TRIM(account) AS account, MIN(tid) AS tid
|
||||
@@ -84,13 +50,6 @@ SET e.tid = u.tid,
|
||||
WHERE e.delete_time IS NULL
|
||||
AND (e.tid IS NULL OR e.tid = 0);
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 3. 同企业内同名老员工账号对齐
|
||||
-- 条件:① 员工账号在本企业没有对应用户(历史手工人员)
|
||||
-- ② 该用户在本企业还没有员工
|
||||
-- ③ 按姓名能唯一匹配到一个用户
|
||||
-- 只改 account,不动 id,历史引用全部保留
|
||||
-- -----------------------------------------------------------------------------
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_emp_align;
|
||||
CREATE TEMPORARY TABLE tmp_emp_align (
|
||||
emp_id BIGINT UNSIGNED NOT NULL PRIMARY KEY,
|
||||
@@ -134,11 +93,6 @@ FROM tmp_emp_align;
|
||||
|
||||
DROP TEMPORARY TABLE IF EXISTS tmp_emp_align;
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 4. 用户仍然没有员工:按用户资料补建员工记录
|
||||
-- 与 services/EnsureEmployeeForTenantUser 的规则一致(账号、姓名、性别、生日、
|
||||
-- 部门、手机、邮箱、启用状态),密码留空(登录走统一认证,不校验员工密码)
|
||||
-- -----------------------------------------------------------------------------
|
||||
INSERT INTO yz_backend_employee
|
||||
(tid, account, password, name, gender, birthday, department, phone, email,
|
||||
account_status, create_time, update_time)
|
||||
@@ -164,9 +118,6 @@ WHERE u.delete_time IS NULL
|
||||
AND TRIM(u.account) <> ''
|
||||
AND e.id IS NULL;
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 5. 复核
|
||||
-- -----------------------------------------------------------------------------
|
||||
SELECT '执行后:用户/员工数量' AS section;
|
||||
SELECT
|
||||
(SELECT COUNT(*) FROM yz_system_tenant_user WHERE delete_time IS NULL) AS user_rows,
|
||||
@@ -178,7 +129,6 @@ SELECT
|
||||
WHERE e.delete_time IS NULL AND e.tid = u.tid AND TRIM(e.account) = TRIM(u.account))
|
||||
) AS user_without_employee;
|
||||
|
||||
-- 按企业对比:用户数 / 员工数 / 本企业无账号的员工数
|
||||
SELECT
|
||||
u.tid,
|
||||
u.user_cnt,
|
||||
@@ -204,12 +154,6 @@ LEFT JOIN (
|
||||
) e ON e.tid = u.tid
|
||||
ORDER BY u.tid;
|
||||
|
||||
-- -----------------------------------------------------------------------------
|
||||
-- 6. 仍需人工确认:员工在本企业没有登录账号(老数据,脚本不删除也不改)
|
||||
-- 处理方式二选一:
|
||||
-- a) 在「用户管理」用相同账号添加用户 → 会自动关联到已有员工档案,不会重复建档
|
||||
-- b) 在「人员管理」把这些人员设为离职(account_status = 2)
|
||||
-- -----------------------------------------------------------------------------
|
||||
SELECT '仍无登录账号的员工' AS section,
|
||||
e.tid, e.id, TRIM(e.account) AS account, TRIM(e.name) AS name,
|
||||
TRIM(IFNULL(e.department, '')) AS department
|
||||
|
||||
@@ -1,64 +1,18 @@
|
||||
-- =============================================================
|
||||
-- 修复:模块「展示端(platforms)」误配置导致菜单整块消失
|
||||
--
|
||||
-- 背景:
|
||||
-- yz_system_modules.platforms 是与 status/is_show、菜单 views、角色 rights
|
||||
-- 并列的第四个维度,决定模块/菜单出现在 Web 端还是移动端:
|
||||
-- ["web"] 仅 Web 端(租户管理后台 PC)
|
||||
-- ["app"] 仅移动端(APP / 微信小程序)
|
||||
-- ["web","app"] 两端都显示
|
||||
-- '' / NULL 全端显示(默认)
|
||||
--
|
||||
-- 菜单自身未配置 platforms 时,按 path 前缀继承所属模块的 platforms
|
||||
-- (services.MenuVisibleOn)。所以模块一旦配错,其下整棵菜单都会被
|
||||
-- 某一端整体剔除——而后台的「模块管理 / 菜单管理 / 角色管理」里
|
||||
-- 所有开关都是正常的,界面上完全看不出原因。
|
||||
--
|
||||
-- 事故原因:
|
||||
-- add_module_platforms.sql 里的「使用示例」第 1、2 条是演示语句,
|
||||
-- 却被原样执行到了正式库:
|
||||
-- 例1 UPDATE yz_system_modules SET platforms = JSON_ARRAY('web') WHERE code = 'crm';
|
||||
-- 例2 UPDATE yz_system_modules SET platforms = JSON_ARRAY('app') WHERE code = 'bianjiegongju';
|
||||
--
|
||||
-- 后果:
|
||||
-- 例2 → 租户后台(Web)左侧菜单里 /tools(便捷工具)整块消失:
|
||||
-- 记事本、日程提醒、账号管理全部不显示。
|
||||
-- 例1 → 移动端工作台没有「客户关系」模块卡片,/apps/crm 下 29 条菜单全部不显示。
|
||||
--
|
||||
-- 修复:两个模块都恢复为两端可见。
|
||||
-- 依据:
|
||||
-- · 便捷工具:backend/src/views/tools/ 有记事本/日程/密码库完整页面;
|
||||
-- uniapp/pages/toolbox/ 有 home/functions/mine/todo;
|
||||
-- 菜单 views 含 2;全部租户套餐都含 bianjiegongju。
|
||||
-- · 客户关系:backend/src/views/apps/crm/ 与 uniapp/pages/crm/ 均已完整实现;
|
||||
-- SUBSYSTEMS 已注册 crm;菜单 views 全为 2(租户端两端共用)。
|
||||
--
|
||||
-- 回滚:
|
||||
-- UPDATE yz_system_modules SET platforms = JSON_ARRAY('app')
|
||||
-- WHERE code = 'bianjiegongju';
|
||||
-- UPDATE yz_system_modules SET platforms = JSON_ARRAY('web')
|
||||
-- WHERE code = 'crm';
|
||||
-- =============================================================
|
||||
|
||||
-- ---------- 修复前先看一眼现状 ----------
|
||||
SELECT id, name, code, path, type, status, is_show, platforms
|
||||
FROM yz_system_modules
|
||||
WHERE code IN ('bianjiegongju', 'crm');
|
||||
|
||||
-- ---------- 恢复为两端可见 ----------
|
||||
UPDATE yz_system_modules
|
||||
SET platforms = JSON_ARRAY('web', 'app'),
|
||||
update_time = NOW()
|
||||
WHERE code IN ('bianjiegongju', 'crm')
|
||||
AND delete_time IS NULL;
|
||||
|
||||
-- ---------- 校验 ----------
|
||||
SELECT id, name, code, path, type, status, is_show, platforms
|
||||
FROM yz_system_modules
|
||||
WHERE code IN ('bianjiegongju', 'crm');
|
||||
|
||||
-- ---------- 顺带体检:其余模块不应残留单端配置 ----------
|
||||
-- 除本次修复的两个模块外,其余模块 platforms 应为 NULL(全端)。
|
||||
SELECT id, name, code, path, platforms
|
||||
FROM yz_system_modules
|
||||
WHERE delete_time IS NULL
|
||||
|
||||
@@ -1,15 +1,4 @@
|
||||
-- 修复:注册「创建企业」审批通过后,申请人登录提示「该账号未绑定任何企业」。
|
||||
--
|
||||
-- 两个叠在一起的 bug:
|
||||
-- ① finishApply 没把新建租户 tid 回写到申请单 → yz_auth_tenant_apply.tid 一直是 0,
|
||||
-- 事后无法按 tid 追溯/修数据(代码已修复)。
|
||||
-- ② 绑定时调用 SyncTenantUser 按「手机/邮箱/账号」归并键匹配身份,账号注册的身份
|
||||
-- 没有手机号、邮箱,企业内账号又是拼出来的 user{id},匹配不到 → 新建了一个身份
|
||||
-- (account=user{id})并绑定到新租户,申请人自己的身份反而没有绑定记录
|
||||
-- (代码已改为按 identity_id 直接写绑定)。
|
||||
-- 本脚本修正【已审批的历史数据】,下列语句均可直接执行,无需替换占位符。
|
||||
|
||||
-- ============ ① 回填申请单的 tid(按企业名称匹配新建的租户) ============
|
||||
UPDATE yz_auth_tenant_apply a
|
||||
JOIN yz_system_tenant t
|
||||
ON t.tenant_name = a.tenant_name AND t.delete_time IS NULL
|
||||
@@ -17,7 +6,6 @@ SET a.tid = t.id, a.update_time = NOW()
|
||||
WHERE a.type = 2 AND a.status = 1 AND a.delete_time IS NULL
|
||||
AND (a.tid = 0 OR a.tid IS NULL);
|
||||
|
||||
-- ============ ② 排查:申请 / 身份 / 绑定 / 租户对照 ============
|
||||
SELECT a.id AS apply_id, a.status AS apply_status, a.tid, a.tenant_name,
|
||||
a.identity_id AS apply_identity, ai.account AS apply_account, ai.mobile AS apply_mobile,
|
||||
tu.id AS bind_id, tu.identity_id AS bind_identity, bi.account AS bind_account,
|
||||
@@ -31,9 +19,7 @@ LEFT JOIN yz_system_tenant t ON t.id = a.tid
|
||||
WHERE a.delete_time IS NULL
|
||||
ORDER BY a.id DESC
|
||||
LIMIT 20;
|
||||
-- 关注:bind_identity 是否 = apply_identity;bind_status=1;bind_deleted=NULL;tenant_status=1
|
||||
|
||||
-- ============ ③ 修正绑错人的行(改指到申请人,并复位状态) ============
|
||||
UPDATE yz_auth_tenant_user tu
|
||||
JOIN yz_auth_tenant_apply a
|
||||
ON a.tid = tu.tid AND a.type = 2 AND a.status = 1 AND a.delete_time IS NULL
|
||||
@@ -41,7 +27,6 @@ SET tu.identity_id = a.identity_id, tu.status = 1, tu.is_default = 1,
|
||||
tu.delete_time = NULL, tu.update_time = NOW()
|
||||
WHERE tu.identity_id <> a.identity_id;
|
||||
|
||||
-- ============ ④ 修正「绑对人但状态异常」的行(status≠1 或已软删) ============
|
||||
UPDATE yz_auth_tenant_user tu
|
||||
JOIN yz_auth_tenant_apply a
|
||||
ON a.tid = tu.tid AND a.type = 2 AND a.status = 1 AND a.delete_time IS NULL
|
||||
@@ -49,7 +34,6 @@ SET tu.status = 1, tu.is_default = 1, tu.delete_time = NULL, tu.update_time = NO
|
||||
WHERE tu.identity_id = a.identity_id
|
||||
AND (tu.status <> 1 OR tu.delete_time IS NOT NULL);
|
||||
|
||||
-- ============ ⑤ 兜底:申请人压根没有绑定行时补一条 ============
|
||||
INSERT INTO yz_auth_tenant_user
|
||||
(tid, identity_id, account, name, phone, email, group_id, org_id, is_default, status, create_time)
|
||||
SELECT a.tid, a.identity_id,
|
||||
@@ -64,7 +48,6 @@ WHERE a.type = 2 AND a.status = 1 AND a.tid > 0 AND a.delete_time IS NULL
|
||||
WHERE tu.tid = a.tid AND tu.identity_id = a.identity_id
|
||||
);
|
||||
|
||||
-- ============ ⑥ 核对:申请人名下应能看到企业 ============
|
||||
SELECT tu.identity_id, tu.tid, tu.status AS bind_status, tu.is_default, tu.group_id,
|
||||
t.tenant_name, t.status AS tenant_status
|
||||
FROM yz_auth_tenant_user tu
|
||||
@@ -72,11 +55,3 @@ JOIN yz_system_tenant t ON t.id = tu.tid
|
||||
JOIN yz_auth_tenant_apply a
|
||||
ON a.tid = tu.tid AND a.type = 2 AND a.status = 1 AND a.identity_id = tu.identity_id;
|
||||
|
||||
-- ============ ⑦ 可选:清理审批时误建的身份(确认无任何绑定后再执行) ============
|
||||
-- SELECT id, account, mobile, last_login_at FROM yz_auth_identity
|
||||
-- WHERE account LIKE 'user%' AND last_login_at IS NULL
|
||||
-- AND NOT EXISTS (SELECT 1 FROM yz_auth_tenant_user tu WHERE tu.identity_id = yz_auth_identity.id);
|
||||
-- DELETE i FROM yz_auth_identity i
|
||||
-- WHERE i.account LIKE 'user%' AND i.last_login_at IS NULL
|
||||
-- AND NOT EXISTS (SELECT 1 FROM yz_auth_tenant_user tu WHERE tu.identity_id = i.id)
|
||||
-- AND NOT EXISTS (SELECT 1 FROM yz_auth_identity_third th WHERE th.identity_id = i.id);
|
||||
@@ -1,16 +1,3 @@
|
||||
-- =============================================================
|
||||
-- 平台官网管理专用上传分组:官网素材
|
||||
--
|
||||
-- 官网管理(platform/src/views/website)下所有图片/文件上传统一归入该分组,
|
||||
-- 便于在「系统管理 → 文件管理」(/system/fileManager) 中集中查找与复用。
|
||||
--
|
||||
-- 归属:tid = 0(平台端),uid = 1(平台管理员),与既有 appsupgrade、图片 分组一致。
|
||||
-- 幂等:已存在同名未删除分组时不会重复插入。
|
||||
-- 运行:mysql -h<host> -P<port> -u<user> -p <db> < init_platform_website_file_cate.sql
|
||||
--
|
||||
-- 备注:前端 utils/websiteUpload.js 也会在上传时按名称兜底查找/补建,
|
||||
-- 因此即使本文件未执行,首次上传后该分组同样会出现。
|
||||
-- =============================================================
|
||||
|
||||
INSERT INTO `yz_system_files_category` (`tid`, `uid`, `name`, `create_time`)
|
||||
SELECT * FROM (
|
||||
|
||||
@@ -1,26 +1,6 @@
|
||||
-- =============================================================
|
||||
-- 租户端数据字典 —— 初始数据(系统内置,全局共享)
|
||||
--
|
||||
-- 表:yz_backend_dict / yz_backend_dict_item(建表见 create_dict.sql)
|
||||
--
|
||||
-- 重要:本文件写入的是 tenant_id = '0' 的「全局内置字典」,与 yz_system_admin_role
|
||||
-- 中 tenant_id=0 的全局租户角色同一套约定:
|
||||
-- - 所有租户都能通过 /backend/dict/options/:code 读到;
|
||||
-- - 租户若需要改动,请按相同 dict_code 新建一份自己的字典(读接口优先取租户自己的,
|
||||
-- 字典管理页里全局字典显示为「内置」只读)。
|
||||
--
|
||||
-- 内容来源:backend 前端散落的硬编码映射,其中 CRM 部分取自 views/apps/crm/dict.js。
|
||||
-- 幂等:字典按 (tenant_id='0', dict_code) 判重,字典项按 (dict_id, item_value) 判重,可重复执行。
|
||||
-- 说明:未给出标签色的字典项 tag_type 留空,可在「系统设置 → 数据字典」里按需补。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 1. 字典列表(全局内置)
|
||||
-- =============================================================
|
||||
|
||||
INSERT INTO `yz_backend_dict` (`tenant_id`, `dict_name`, `dict_code`, `remark`, `sort`, `status`, `create_user_id`, `create_time`)
|
||||
SELECT '0', t.dict_name, t.dict_code, t.remark, t.sort, 1, 'sql', NOW()
|
||||
FROM (
|
||||
@@ -108,11 +88,6 @@ WHERE NOT EXISTS (
|
||||
WHERE d.tenant_id = '0' AND d.dict_code = t.dict_code AND d.delete_time IS NULL
|
||||
);
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 2. 字典项(全局内置)
|
||||
-- =============================================================
|
||||
|
||||
INSERT INTO `yz_backend_dict_item` (`tenant_id`, `dict_id`, `item_label`, `item_value`, `tag_type`, `sort`, `status`, `is_default`, `create_time`)
|
||||
SELECT '0', d.id, t.item_label, t.item_value, t.tag_type, t.sort, 1, 0, NOW()
|
||||
FROM (
|
||||
@@ -435,11 +410,6 @@ WHERE NOT EXISTS (
|
||||
WHERE i.dict_id = d.id AND i.item_value = t.item_value AND i.delete_time IS NULL
|
||||
);
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 3. 校验
|
||||
-- =============================================================
|
||||
|
||||
SELECT d.dict_name, d.dict_code, COUNT(i.id) AS item_count
|
||||
FROM `yz_backend_dict` d
|
||||
LEFT JOIN `yz_backend_dict_item` i ON i.dict_id = d.id AND i.delete_time IS NULL
|
||||
|
||||
@@ -1,35 +1,11 @@
|
||||
-- =============================================================
|
||||
-- 平台端数据字典 —— 初始数据
|
||||
--
|
||||
-- 表:yz_platform_dict / yz_platform_dict_item(建表见 create_dict.sql)
|
||||
-- 内容来源:platform 前端散落的硬编码映射(值→文案 / 标签色),
|
||||
-- 以及各平台端接口返回的状态字段取值。
|
||||
--
|
||||
-- 幂等:
|
||||
-- - 字典按 dict_code 判重,已存在则跳过;
|
||||
-- - 字典项按 (dict_id, item_value) 判重,已存在则跳过。
|
||||
-- 因此可重复执行,不会产生重复数据。
|
||||
--
|
||||
-- 说明:
|
||||
-- - tag_type 对应前端 el-tag 的 type,留空表示不渲染彩色标签;
|
||||
-- - sort 按 10 递增,便于后续插入新字典项;
|
||||
-- - 执行完这份数据后,前端改为调用 /platform/dict/options/:code 读取。
|
||||
-- =============================================================
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 1. 字典列表
|
||||
-- =============================================================
|
||||
|
||||
INSERT INTO `yz_platform_dict` (`dict_name`, `dict_code`, `remark`, `sort`, `status`, `create_user_id`, `create_time`)
|
||||
SELECT t.dict_name, t.dict_code, t.remark, t.sort, 1, 'sql', NOW()
|
||||
FROM (
|
||||
-- 通用
|
||||
SELECT '通用启用状态' AS dict_name, 'common_enable_status' AS dict_code, '1 启用 / 0 停用,部分页面把 0 显示为「禁用」' AS remark, 10 AS sort
|
||||
UNION ALL SELECT '是否' , 'common_yes_no' , '1 是 / 0 否' , 20
|
||||
-- 支付
|
||||
UNION ALL SELECT '支付渠道' , 'payment_channel' , 'yz_platform_payment_channel.channel' , 100
|
||||
UNION ALL SELECT '支付单状态' , 'payment_order_status' , 'yz_platform_payment_order.status' , 110
|
||||
UNION ALL SELECT '支付订单类型' , 'payment_order_type' , 'yz_platform_payment_order.order_type' , 120
|
||||
@@ -39,20 +15,16 @@ FROM (
|
||||
UNION ALL SELECT '佣金状态' , 'payment_commission_status', 'yz_platform_commission_order.status' , 160
|
||||
UNION ALL SELECT '佣金发放方式' , 'payment_commission_pay_method', 'yz_platform_commission_order.pay_method' , 170
|
||||
UNION ALL SELECT '佣金计算方式' , 'payment_calc_type' , 'yz_platform_commission_rule.calc_type' , 180
|
||||
-- 通知 / 短信
|
||||
UNION ALL SELECT '通知渠道' , 'notification_channel' , '站内提醒的推送渠道' , 200
|
||||
UNION ALL SELECT '短信任务状态' , 'sms_task_status' , 'yz_system_sms_task.status' , 210
|
||||
-- 系统
|
||||
UNION ALL SELECT '请求方法' , 'http_method' , '操作日志的 HTTP 方法' , 220
|
||||
UNION ALL SELECT '登录方式' , 'login_type' , '登录日志的登录方式' , 230
|
||||
UNION ALL SELECT '菜单类型' , 'menu_type' , 'yz_system_menu.type' , 240
|
||||
-- 官网内容
|
||||
UNION ALL SELECT '导航类型' , 'website_nav_type' , 'yz_platform_website_nav.type' , 250
|
||||
UNION ALL SELECT '评论状态' , 'comment_status' , 'yz_platform_website_comment.status' , 260
|
||||
UNION ALL SELECT '文章状态' , 'article_status' , 'yz_platform_website_article.status' , 270
|
||||
UNION ALL SELECT '公告类型' , 'notice_type' , 'yz_platform_website_notice.type' , 280
|
||||
UNION ALL SELECT '公告状态' , 'notice_status' , 'yz_platform_website_notice.status' , 290
|
||||
-- 账号池 / Cursor
|
||||
UNION ALL SELECT '账号池平台' , 'account_pool_platform' , '账号来源平台(本地/闲鱼/淘宝…)' , 300
|
||||
UNION ALL SELECT '账号池数据类型' , 'account_pool_data_type' , '账号密码 / 账号密码+Token / Token' , 310
|
||||
UNION ALL SELECT '账号池提取状态' , 'account_pool_extract_status', '账号池记录的提取状态' , 320
|
||||
@@ -60,19 +32,14 @@ FROM (
|
||||
UNION ALL SELECT 'Cursor 激活码状态' , 'cursor_activation_status' , 'yz_platform_cursor_activation_code.status' , 340
|
||||
UNION ALL SELECT '提取记录状态' , 'cursor_extract_record_status', 'Cursor 设备提取记录的状态' , 350
|
||||
UNION ALL SELECT '激活记录状态' , 'cursor_activation_record_status', 'Cursor 设备激活记录的状态' , 360
|
||||
-- 模块商店
|
||||
UNION ALL SELECT '模块发布状态' , 'moduleshop_publish_status' , '模块商店上下架状态' , 370
|
||||
UNION ALL SELECT '模块分类状态' , 'moduleshop_category_status' , '模块商店分类启用状态' , 380
|
||||
-- 投诉工单
|
||||
UNION ALL SELECT '投诉工单状态' , 'complain_status' , 'yz_platform_complaint.status' , 390
|
||||
-- 统一认证
|
||||
UNION ALL SELECT '接入应用类型' , 'auth_app_type' , 'yz_auth_client.app_type' , 400
|
||||
UNION ALL SELECT '认证域' , 'auth_realm' , '租户域 / 平台域' , 410
|
||||
UNION ALL SELECT '登录验证方式' , 'auth_verify_type' , '图形验证码 / 短信 / 邮箱 / 极验 / 不开启' , 420
|
||||
-- 域名
|
||||
UNION ALL SELECT '域名类型' , 'domain_type' , 'yz_system_tenant_domain.domain_type' , 430
|
||||
UNION ALL SELECT '域名状态' , 'domain_status' , 'yz_system_tenant_domain.status' , 440
|
||||
-- 租户 / 组织
|
||||
UNION ALL SELECT '员工状态' , 'employee_status' , 'yz_backend_employee.account_status' , 450
|
||||
UNION ALL SELECT '性别' , 'gender' , '用户/员工性别' , 460
|
||||
UNION ALL SELECT '角色分类' , 'role_category' , 'yz_system_admin_role.cid:1 平台角色 / 2 租户角色' , 470
|
||||
@@ -84,27 +51,18 @@ WHERE NOT EXISTS (
|
||||
WHERE d.dict_code = t.dict_code AND d.delete_time IS NULL
|
||||
);
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 2. 字典项
|
||||
-- =============================================================
|
||||
|
||||
INSERT INTO `yz_platform_dict_item` (`dict_id`, `item_label`, `item_value`, `tag_type`, `sort`, `status`, `is_default`, `create_time`)
|
||||
SELECT d.id, t.item_label, t.item_value, t.tag_type, t.sort, 1, 0, NOW()
|
||||
FROM (
|
||||
-- 通用启用状态
|
||||
SELECT 'common_enable_status' AS dict_code, '启用' AS item_label, '1' AS item_value, 'success' AS tag_type, 10 AS sort
|
||||
UNION ALL SELECT 'common_enable_status' , '停用' , '0' , 'info' , 20
|
||||
-- 是否
|
||||
UNION ALL SELECT 'common_yes_no' , '是' , '1' , 'success' , 10
|
||||
UNION ALL SELECT 'common_yes_no' , '否' , '0' , 'info' , 20
|
||||
-- 支付渠道
|
||||
UNION ALL SELECT 'payment_channel' , '微信支付' , 'wechat' , '' , 10
|
||||
UNION ALL SELECT 'payment_channel' , '支付宝' , 'alipay' , '' , 20
|
||||
UNION ALL SELECT 'payment_channel' , '银联' , 'unionpay' , '' , 30
|
||||
UNION ALL SELECT 'payment_channel' , '云闪付' , 'cloudpay' , '' , 40
|
||||
UNION ALL SELECT 'payment_channel' , 'PayPal' , 'paypal' , '' , 50
|
||||
-- 支付单状态
|
||||
UNION ALL SELECT 'payment_order_status' , '已创建' , 'created' , 'info' , 10
|
||||
UNION ALL SELECT 'payment_order_status' , '待支付' , 'pending' , 'warning' , 20
|
||||
UNION ALL SELECT 'payment_order_status' , '支付中' , 'paying' , 'warning' , 30
|
||||
@@ -116,84 +74,66 @@ FROM (
|
||||
UNION ALL SELECT 'payment_order_status' , '退款中' , 'refunding' , 'warning' , 90
|
||||
UNION ALL SELECT 'payment_order_status' , '已退款' , 'refunded' , 'info' , 100
|
||||
UNION ALL SELECT 'payment_order_status' , '部分退款' , 'partial_refunded' , 'warning' , 110
|
||||
-- 支付订单类型
|
||||
UNION ALL SELECT 'payment_order_type' , '平台使用费' , 'platform_usage' , '' , 10
|
||||
UNION ALL SELECT 'payment_order_type' , '模块购买' , 'module_shop' , '' , 20
|
||||
UNION ALL SELECT 'payment_order_type' , '服务费' , 'service_fee' , '' , 30
|
||||
-- 支付渠道状态
|
||||
UNION ALL SELECT 'payment_channel_state' , '已启用' , 'enabled' , 'success' , 10
|
||||
UNION ALL SELECT 'payment_channel_state' , '已停用' , 'disabled' , 'info' , 20
|
||||
UNION ALL SELECT 'payment_channel_state' , '未配置' , 'unconfigured' , 'warning' , 30
|
||||
-- 对账处理状态
|
||||
UNION ALL SELECT 'payment_reconcile_status' , '待处理' , 'unhandled' , 'warning' , 10
|
||||
UNION ALL SELECT 'payment_reconcile_status' , '处理中' , 'handling' , 'primary' , 20
|
||||
UNION ALL SELECT 'payment_reconcile_status' , '已处理' , 'handled' , 'success' , 30
|
||||
UNION ALL SELECT 'payment_reconcile_status' , '已忽略' , 'ignored' , 'info' , 40
|
||||
-- 对账差异类型
|
||||
UNION ALL SELECT 'payment_reconcile_diff_type' , '长款' , 'long' , 'warning' , 10
|
||||
UNION ALL SELECT 'payment_reconcile_diff_type' , '短款' , 'short' , 'danger' , 20
|
||||
UNION ALL SELECT 'payment_reconcile_diff_type' , '状态不一致' , 'status_mismatch' , 'warning' , 30
|
||||
-- 佣金状态
|
||||
UNION ALL SELECT 'payment_commission_status' , '应付' , 'payable' , 'warning' , 10
|
||||
UNION ALL SELECT 'payment_commission_status' , '已付' , 'settled' , 'success' , 20
|
||||
UNION ALL SELECT 'payment_commission_status' , '税务处理中' , 'tax_processing' , 'primary' , 30
|
||||
UNION ALL SELECT 'payment_commission_status' , '已作废' , 'canceled' , 'info' , 40
|
||||
-- 佣金发放方式
|
||||
UNION ALL SELECT 'payment_commission_pay_method', '余额抵扣' , 'balance' , '' , 10
|
||||
UNION ALL SELECT 'payment_commission_pay_method', '银行转账' , 'bank' , '' , 20
|
||||
UNION ALL SELECT 'payment_commission_pay_method', '人工发放' , 'manual' , '' , 30
|
||||
UNION ALL SELECT 'payment_commission_pay_method', '下期抵扣' , 'offset' , '' , 40
|
||||
-- 佣金计算方式
|
||||
UNION ALL SELECT 'payment_calc_type' , '按比例' , 'percent' , 'primary' , 10
|
||||
UNION ALL SELECT 'payment_calc_type' , '固定金额' , 'fixed' , 'success' , 20
|
||||
UNION ALL SELECT 'payment_calc_type' , '阶梯' , 'tiered' , 'warning' , 30
|
||||
-- 通知渠道
|
||||
UNION ALL SELECT 'notification_channel' , '短信' , 'SMS' , 'success' , 10
|
||||
UNION ALL SELECT 'notification_channel' , '邮件' , 'EMAIL' , 'warning' , 20
|
||||
UNION ALL SELECT 'notification_channel' , 'Bark推送' , 'BARK' , 'danger' , 30
|
||||
UNION ALL SELECT 'notification_channel' , '站内信' , 'SITE_MSG' , 'primary' , 40
|
||||
-- 短信任务状态
|
||||
UNION ALL SELECT 'sms_task_status' , '待发送' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'sms_task_status' , '发送中' , '1' , 'warning' , 20
|
||||
UNION ALL SELECT 'sms_task_status' , '发送失败' , '2' , 'danger' , 30
|
||||
UNION ALL SELECT 'sms_task_status' , '发送成功' , '3' , 'success' , 40
|
||||
-- 请求方法
|
||||
UNION ALL SELECT 'http_method' , 'GET' , 'GET' , 'info' , 10
|
||||
UNION ALL SELECT 'http_method' , 'POST' , 'POST' , 'success' , 20
|
||||
UNION ALL SELECT 'http_method' , 'PUT' , 'PUT' , 'warning' , 30
|
||||
UNION ALL SELECT 'http_method' , 'DELETE' , 'DELETE' , 'danger' , 40
|
||||
UNION ALL SELECT 'http_method' , 'PATCH' , 'PATCH' , 'primary' , 50
|
||||
-- 登录方式
|
||||
UNION ALL SELECT 'login_type' , '密码登录' , 'password' , '' , 10
|
||||
UNION ALL SELECT 'login_type' , '短信验证码' , 'sms' , '' , 20
|
||||
UNION ALL SELECT 'login_type' , '邮箱验证码' , 'email' , '' , 30
|
||||
-- 菜单类型
|
||||
UNION ALL SELECT 'menu_type' , '目录' , '1' , 'primary' , 10
|
||||
UNION ALL SELECT 'menu_type' , '页面' , '2' , 'success' , 20
|
||||
UNION ALL SELECT 'menu_type' , '接口' , '3' , 'info' , 30
|
||||
-- 导航类型
|
||||
UNION ALL SELECT 'website_nav_type' , '目录' , '1' , 'primary' , 10
|
||||
UNION ALL SELECT 'website_nav_type' , '页面' , '2' , 'success' , 20
|
||||
UNION ALL SELECT 'website_nav_type' , '外链' , '3' , 'info' , 30
|
||||
UNION ALL SELECT 'website_nav_type' , '单页' , '4' , 'warning' , 40
|
||||
-- 评论状态
|
||||
UNION ALL SELECT 'comment_status' , '待审核' , '0' , 'warning' , 10
|
||||
UNION ALL SELECT 'comment_status' , '已通过' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'comment_status' , '已拒绝' , '2' , 'danger' , 30
|
||||
-- 文章状态
|
||||
UNION ALL SELECT 'article_status' , '草稿' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'article_status' , '待审核' , '1' , 'warning' , 20
|
||||
UNION ALL SELECT 'article_status' , '已发布' , '2' , 'success' , 30
|
||||
UNION ALL SELECT 'article_status' , '已隐藏' , '3' , 'danger' , 40
|
||||
-- 公告类型
|
||||
UNION ALL SELECT 'notice_type' , '通知公告' , '1' , '' , 10
|
||||
UNION ALL SELECT 'notice_type' , '活动公告' , '2' , '' , 20
|
||||
UNION ALL SELECT 'notice_type' , '系统维护' , '3' , '' , 30
|
||||
-- 公告状态
|
||||
UNION ALL SELECT 'notice_status' , '草稿' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'notice_status' , '已发布' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'notice_status' , '已下线' , '2' , 'warning' , 30
|
||||
-- 账号池平台
|
||||
UNION ALL SELECT 'account_pool_platform' , '本地' , 'local' , 'info' , 10
|
||||
UNION ALL SELECT 'account_pool_platform' , '闲鱼' , 'xianyu' , 'warning' , 20
|
||||
UNION ALL SELECT 'account_pool_platform' , '拼多多' , 'pinduoduo' , 'danger' , 30
|
||||
@@ -202,81 +142,62 @@ FROM (
|
||||
UNION ALL SELECT 'account_pool_platform' , '淘宝' , 'taobao' , 'info' , 60
|
||||
UNION ALL SELECT 'account_pool_platform' , '自有商城' , 'ziyoushangcheng' , 'warning' , 70
|
||||
UNION ALL SELECT 'account_pool_platform' , '续杯' , 'xubei' , 'primary' , 80
|
||||
-- 账号池数据类型
|
||||
UNION ALL SELECT 'account_pool_data_type' , '账号密码' , 'account' , 'success' , 10
|
||||
UNION ALL SELECT 'account_pool_data_type' , '账号密码+Token' , 'account_tk' , 'primary' , 20
|
||||
UNION ALL SELECT 'account_pool_data_type' , 'Token' , 'tk' , 'warning' , 30
|
||||
-- 账号池提取状态
|
||||
UNION ALL SELECT 'account_pool_extract_status' , '未提取' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'account_pool_extract_status' , '补号' , '2' , 'warning' , 20
|
||||
UNION ALL SELECT 'account_pool_extract_status' , '续杯' , '3' , 'primary' , 30
|
||||
UNION ALL SELECT 'account_pool_extract_status' , '已提取' , 'extracted' , 'success' , 40
|
||||
-- Cursor 设备状态
|
||||
UNION ALL SELECT 'cursor_equipment_status' , '已激活' , 'active' , 'success' , 10
|
||||
UNION ALL SELECT 'cursor_equipment_status' , '未激活' , 'inactive' , 'info' , 20
|
||||
UNION ALL SELECT 'cursor_equipment_status' , '禁用' , 'disabled' , 'danger' , 30
|
||||
UNION ALL SELECT 'cursor_equipment_status' , '已过期' , 'expired' , 'warning' , 40
|
||||
-- Cursor 激活码状态
|
||||
UNION ALL SELECT 'cursor_activation_status' , '未使用' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'cursor_activation_status' , '已使用' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'cursor_activation_status' , '已过期' , '2' , 'warning' , 30
|
||||
UNION ALL SELECT 'cursor_activation_status' , '已禁用' , '3' , 'danger' , 40
|
||||
-- 提取记录状态
|
||||
UNION ALL SELECT 'cursor_extract_record_status', '未提取' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'cursor_extract_record_status', '已提取' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'cursor_extract_record_status', '补号' , '2' , 'warning' , 30
|
||||
UNION ALL SELECT 'cursor_extract_record_status', '异常' , '3' , 'danger' , 40
|
||||
-- 激活记录状态
|
||||
UNION ALL SELECT 'cursor_activation_record_status', '失败' , '0' , 'danger' , 10
|
||||
UNION ALL SELECT 'cursor_activation_record_status', '成功' , '1' , 'success' , 20
|
||||
-- 模块发布状态
|
||||
UNION ALL SELECT 'moduleshop_publish_status' , '草稿' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'moduleshop_publish_status' , '已发布' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'moduleshop_publish_status' , '已撤回' , '2' , 'warning' , 30
|
||||
-- 模块分类状态
|
||||
UNION ALL SELECT 'moduleshop_category_status' , '禁用' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'moduleshop_category_status' , '启用' , '1' , 'success' , 20
|
||||
-- 投诉工单状态
|
||||
UNION ALL SELECT 'complain_status' , '待处理' , '0' , 'warning' , 10
|
||||
UNION ALL SELECT 'complain_status' , '处理中' , '1' , 'warning' , 20
|
||||
UNION ALL SELECT 'complain_status' , '已回复' , '2' , 'success' , 30
|
||||
UNION ALL SELECT 'complain_status' , '已关闭' , '3' , 'info' , 40
|
||||
-- 接入应用类型
|
||||
UNION ALL SELECT 'auth_app_type' , 'Web 后端' , '1' , '' , 10
|
||||
UNION ALL SELECT 'auth_app_type' , 'SPA' , '2' , '' , 20
|
||||
UNION ALL SELECT 'auth_app_type' , '原生 APP' , '3' , '' , 30
|
||||
UNION ALL SELECT 'auth_app_type' , '小程序' , '4' , '' , 40
|
||||
-- 认证域
|
||||
UNION ALL SELECT 'auth_realm' , '租户域' , 'tenant' , '' , 10
|
||||
UNION ALL SELECT 'auth_realm' , '平台域' , 'platform' , '' , 20
|
||||
-- 登录验证方式
|
||||
UNION ALL SELECT 'auth_verify_type' , '图形验证码' , 'captcha' , '' , 10
|
||||
UNION ALL SELECT 'auth_verify_type' , '短信验证码' , 'sms' , '' , 20
|
||||
UNION ALL SELECT 'auth_verify_type' , '邮箱验证码' , 'email' , '' , 30
|
||||
UNION ALL SELECT 'auth_verify_type' , '极验人机验证' , 'geetest' , '' , 40
|
||||
UNION ALL SELECT 'auth_verify_type' , '不开启' , 'none' , '' , 50
|
||||
-- 域名类型
|
||||
UNION ALL SELECT 'domain_type' , '平台二级域名' , '1' , '' , 10
|
||||
UNION ALL SELECT 'domain_type' , '自有域名' , '2' , '' , 20
|
||||
-- 域名状态
|
||||
UNION ALL SELECT 'domain_status' , '审核中' , '0' , 'warning' , 10
|
||||
UNION ALL SELECT 'domain_status' , '已生效' , '1' , 'success' , 20
|
||||
UNION ALL SELECT 'domain_status' , '已禁用' , '2' , 'info' , 30
|
||||
-- 员工状态
|
||||
UNION ALL SELECT 'employee_status' , '启用' , '1' , 'success' , 10
|
||||
UNION ALL SELECT 'employee_status' , '禁用' , '0' , 'info' , 20
|
||||
UNION ALL SELECT 'employee_status' , '离职' , '2' , 'danger' , 30
|
||||
-- 性别
|
||||
UNION ALL SELECT 'gender' , '保密' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'gender' , '男' , '1' , 'primary' , 20
|
||||
UNION ALL SELECT 'gender' , '女' , '2' , 'danger' , 30
|
||||
-- 角色分类
|
||||
UNION ALL SELECT 'role_category' , '平台角色' , '1' , 'primary' , 10
|
||||
UNION ALL SELECT 'role_category' , '租户角色' , '2' , 'warning' , 20
|
||||
-- 角色来源
|
||||
UNION ALL SELECT 'role_source' , '预置' , '0' , 'info' , 10
|
||||
UNION ALL SELECT 'role_source' , '自建' , '1' , 'warning' , 20
|
||||
-- 站内信接收对象
|
||||
UNION ALL SELECT 'sitereminder_target_type' , '全平台(所有人)' , 'all' , 'danger' , 10
|
||||
UNION ALL SELECT 'sitereminder_target_type' , '平台端(所有人)' , 'platform' , 'primary' , 20
|
||||
UNION ALL SELECT 'sitereminder_target_type' , '租户端(所有租户)' , 'tenant_all' , 'success' , 30
|
||||
@@ -292,11 +213,6 @@ WHERE NOT EXISTS (
|
||||
WHERE i.dict_id = d.id AND i.item_value = t.item_value AND i.delete_time IS NULL
|
||||
);
|
||||
|
||||
|
||||
-- =============================================================
|
||||
-- 3. 校验
|
||||
-- =============================================================
|
||||
|
||||
SELECT d.dict_name, d.dict_code, COUNT(i.id) AS item_count
|
||||
FROM `yz_platform_dict` d
|
||||
LEFT JOIN `yz_platform_dict_item` i ON i.dict_id = d.id AND i.delete_time IS NULL
|
||||
|
||||
@@ -1,23 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA AI 办公 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_ai_menus.sql
|
||||
--
|
||||
-- 挂载位置:
|
||||
-- OA → 办公 → AI办公(页面,/apps/oa/ai)
|
||||
-- OA → 基础设置 → AI设置(页面,/basic-settings/ai)
|
||||
--
|
||||
-- 对应页面:
|
||||
-- backend/src/views/apps/oa/ai/index.vue AI 广场(场景对话)
|
||||
-- backend/src/views/basicSettings/ai/index.vue AI 设置(租户级接口 + Key)
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. AI 接入配置是租户级的(yz_backend_ai_provider.user_id = 0),
|
||||
-- 由「AI设置」页统一维护,保存后全租户共用;
|
||||
-- 2. 「AI办公」是 Web 页面(platforms=["web"]),移动端暂不提供;
|
||||
-- 3. 租户端角色(cid=2)的 rights 是显式菜单 ID 列表,只插菜单不授权
|
||||
-- 会被过滤掉,因此本脚本把菜单 ID 追加到角色 rights。
|
||||
-- ============================================================
|
||||
|
||||
SET @oa_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -25,7 +5,6 @@ SET @oa_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- 「办公」目录:优先同名菜单,其次 /apps/oa/personal;都没有则回落 OA 根
|
||||
SET @office_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
@@ -35,7 +14,6 @@ SET @office_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- OA 基础设置目录(AI 设置挂这里)
|
||||
SET @basic_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
WHERE path = '/apps/oa/normalsetting' AND delete_time IS NULL
|
||||
@@ -45,7 +23,6 @@ SET @basic_id := (
|
||||
SET @office_parent := IFNULL(@office_id, @oa_id);
|
||||
SET @basic_parent := IFNULL(@basic_id, @office_parent);
|
||||
|
||||
-- ---------- AI办公(页面,挂在办公下) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @office_parent, 'AI办公', '/apps/oa/ai', '/apps/oa/ai/index.vue',
|
||||
@@ -68,7 +45,6 @@ SET pid = IFNULL(@office_parent, pid),
|
||||
is_visible = 1
|
||||
WHERE path = '/apps/oa/ai' AND delete_time IS NULL;
|
||||
|
||||
-- ---------- AI设置(页面,挂在 OA 基础设置下) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @basic_parent, 'AI设置', '/basic-settings/ai', '/basicSettings/ai/index.vue',
|
||||
@@ -91,8 +67,6 @@ SET pid = IFNULL(@basic_parent, pid),
|
||||
is_visible = 1
|
||||
WHERE path = '/basic-settings/ai' AND delete_time IS NULL;
|
||||
|
||||
-- ---------- 角色授权:把菜单追加到所有租户端角色的 rights ----------
|
||||
-- 只处理 rights 非空(显式授权)的角色;rights 为空表示全权限,无需追加。
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CAST(JSON_ARRAY_APPEND(CAST(rights AS JSON), '$', @ai_page_id) AS CHAR)
|
||||
WHERE cid = 2
|
||||
@@ -107,7 +81,6 @@ WHERE cid = 2
|
||||
AND @ai_settings_id IS NOT NULL
|
||||
AND NOT JSON_CONTAINS(CAST(rights AS JSON), CAST(@ai_settings_id AS JSON));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, platforms, type, sort, is_visible
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
|
||||
@@ -1,14 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA 审批中心 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_approvalcenter_menus.sql
|
||||
--
|
||||
-- 对应页面:
|
||||
-- /apps/oa/approvalcenter/mine 我的发起(我提交的单据)
|
||||
-- /apps/oa/approvalcenter/list 审批列表(待我审批 / 我已处理)
|
||||
-- /apps/oa/approvalcenter/settings 审批流设置(复用系统管理的编排能力)
|
||||
-- 注意:目录本身依赖 OA 应用根菜单 '/apps/oa',缺失时脚本不会写入任何数据。
|
||||
-- ============================================================
|
||||
|
||||
SET @oa_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -16,7 +5,6 @@ SET @oa_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 审批中心(目录) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @oa_id, '审批中心', '/apps/oa/approvalcenter', NULL,
|
||||
@@ -31,7 +19,6 @@ SET @center_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 我的发起 ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @center_id, '我的发起', '/apps/oa/approvalcenter/mine', 'apps/oa/approvalcenter/mine.vue',
|
||||
@@ -40,7 +27,6 @@ FROM DUAL
|
||||
WHERE @center_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/approvalcenter/mine' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 审批列表 ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @center_id, '审批列表', '/apps/oa/approvalcenter/list', 'apps/oa/approvalcenter/list.vue',
|
||||
@@ -49,7 +35,6 @@ FROM DUAL
|
||||
WHERE @center_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/approvalcenter/list' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 审批流设置 ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT @center_id, '审批流设置', '/apps/oa/approvalcenter/settings', 'apps/oa/approvalcenter/settings.vue',
|
||||
@@ -58,7 +43,6 @@ FROM DUAL
|
||||
WHERE @center_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/approvalcenter/settings' AND delete_time IS NULL) x);
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, type, sort
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path LIKE '/apps/oa/approvalcenter%'
|
||||
|
||||
@@ -1,30 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA 考勤管理 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_attendance_menus.sql
|
||||
--
|
||||
-- 挂载位置:OA → 办公(个人办公),直接是页面,不再套「排班考勤」目录
|
||||
-- OA
|
||||
-- └─ 办公(/apps/oa/personal,找不到时回落到 OA 根)
|
||||
-- ├─ 工作排班(Web,/apps/oa/scheduling/board)
|
||||
-- ├─ 考勤管理(Web,/apps/oa/attendance) ← 本脚本
|
||||
-- └─ 考勤打卡(App,/apps/oa/attendance/clock) ← 本脚本
|
||||
--
|
||||
-- 页面:
|
||||
-- backend/src/views/apps/oa/attendance/index.vue 考勤管理(考勤汇总 + 考勤明细)
|
||||
-- uniapp/pages/oa/attendance/index.vue 考勤打卡(移动端)
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. 「考勤管理」是直接页面(type=2),点菜单即打开,不再有子菜单;
|
||||
-- 2. 打卡动作在移动端完成,Web 端只做考勤汇总 / 明细 / 缺卡名单 / 备注,
|
||||
-- 因此「考勤管理」platforms 为 ["web"];
|
||||
-- 3. 「考勤打卡」platforms 为 ["app"],通过 uniapp 菜单跳转原生页面
|
||||
-- (uniapp/utils/nav.js 的 NATIVE_RULES 按「考勤」匹配);
|
||||
-- 4. 历史版本创建的「排班考勤」目录不再使用,脚本会把它隐藏(保留数据);
|
||||
-- 其下的「工作排班」直接上移到「办公」;
|
||||
-- 5. 租户端角色(cid=2)的 rights 是显式菜单 ID 列表,只插菜单不授权
|
||||
-- 会被过滤掉,因此本脚本把菜单 ID 追加到角色 rights。
|
||||
-- ============================================================
|
||||
|
||||
SET @oa_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -32,7 +5,6 @@ SET @oa_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- 「办公」目录:优先同名菜单,其次 /apps/oa/personal;都没有则回落 OA 根
|
||||
SET @office_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
@@ -44,7 +16,6 @@ SET @office_id := (
|
||||
|
||||
SET @parent_id := IFNULL(@office_id, @oa_id);
|
||||
|
||||
-- ---------- 考勤管理(Web 页面,直接挂在办公下) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @parent_id, '考勤管理', '/apps/oa/attendance', '/apps/oa/attendance/index.vue',
|
||||
@@ -54,7 +25,6 @@ FROM DUAL
|
||||
WHERE @parent_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/attendance' AND delete_time IS NULL) x);
|
||||
|
||||
-- 已存在则纠正为「直接页面」:改名、上移、确保是页面与 Web 端可见
|
||||
UPDATE yz_system_menu
|
||||
SET title = '考勤管理',
|
||||
pid = IFNULL(@parent_id, pid),
|
||||
@@ -71,7 +41,6 @@ SET @records_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 考勤打卡(移动端页面,同样直接挂在办公下) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @parent_id, '考勤打卡', '/apps/oa/attendance/clock', NULL,
|
||||
@@ -94,7 +63,6 @@ SET @clock_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 工作排班上移:不再保留「排班考勤」目录 ----------
|
||||
UPDATE yz_system_menu
|
||||
SET pid = IFNULL(@parent_id, pid), sort = 88
|
||||
WHERE path = '/apps/oa/scheduling/board'
|
||||
@@ -102,8 +70,6 @@ WHERE path = '/apps/oa/scheduling/board'
|
||||
AND @parent_id IS NOT NULL
|
||||
AND (pid IS NULL OR pid <> @parent_id);
|
||||
|
||||
-- 历史的「排班考勤」目录:不再使用,隐藏(保留数据,避免影响已有角色授权)
|
||||
-- 仅当目录下已无可见子菜单时才隐藏,避免误伤租户自行添加的子菜单
|
||||
UPDATE yz_system_menu
|
||||
SET is_visible = 0
|
||||
WHERE path = '/apps/oa/scheduling'
|
||||
@@ -122,8 +88,6 @@ SET @board_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 角色授权:把菜单追加到所有租户端角色的 rights ----------
|
||||
-- 只处理 rights 非空(显式授权)的角色;rights 为空表示全权限,无需追加。
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CAST(JSON_ARRAY_APPEND(CAST(rights AS JSON), '$', @records_id) AS CHAR)
|
||||
WHERE cid = 2
|
||||
@@ -145,7 +109,6 @@ WHERE cid = 2
|
||||
AND @board_id IS NOT NULL
|
||||
AND NOT JSON_CONTAINS(CAST(rights AS JSON), CAST(@board_id AS JSON));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, platforms, type, sort, is_visible
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
|
||||
@@ -1,17 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA 工作日报 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_dailyreport_menus.sql
|
||||
--
|
||||
-- 挂载位置:OA → 个人办公(path = '/apps/oa/personal')
|
||||
-- 页面:我的日报 + 团队日报(同一页面内 Tab,团队 Tab 由接口权限决定是否显示)
|
||||
-- 说明:platforms 显式声明为 Web + APP(JSON:["web","app"]),小程序端
|
||||
-- 通过 utils/nav.js 的原生规则跳转到 pages/oa/dailyreport/index。
|
||||
--
|
||||
-- 注意:租户端角色(cid=2)的 rights 是显式菜单 ID 列表,菜单接口会按
|
||||
-- rights 过滤。只插菜单不授权,会导致「个人办公」目录可见但
|
||||
-- 「工作日报」被过滤掉。因此本脚本同时把菜单 ID 追加到角色 rights。
|
||||
-- ============================================================
|
||||
|
||||
SET @personal_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -28,7 +14,6 @@ FROM DUAL
|
||||
WHERE @personal_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/dailyreport' AND delete_time IS NULL) x);
|
||||
|
||||
-- 已有菜单的组件路径统一为带前导斜杠(与个人办公下其他菜单一致)
|
||||
UPDATE yz_system_menu
|
||||
SET component_path = '/apps/oa/dailyreport/index.vue'
|
||||
WHERE path = '/apps/oa/dailyreport'
|
||||
@@ -41,8 +26,6 @@ SET @report_menu_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 角色授权:把菜单追加到所有租户端角色的 rights ----------
|
||||
-- 只处理 rights 非空(显式授权)的角色;rights 为空表示全权限,无需追加。
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CAST(JSON_ARRAY_APPEND(CAST(rights AS JSON), '$', @report_menu_id) AS CHAR)
|
||||
WHERE cid = 2
|
||||
@@ -52,7 +35,6 @@ WHERE cid = 2
|
||||
AND @report_menu_id IS NOT NULL
|
||||
AND NOT JSON_CONTAINS(CAST(rights AS JSON), CAST(@report_menu_id AS JSON));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, platforms, type, sort
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path = '/apps/oa/dailyreport';
|
||||
|
||||
@@ -1,26 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA 职级管理 —— 菜单配置(yz_system_menu)
|
||||
--
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_job_rank_menus.sql
|
||||
--
|
||||
-- 挂载位置:OA → 基础设置(目录,path = '/apps/oa/normalsetting')
|
||||
-- OA
|
||||
-- └─ 基础设置
|
||||
-- ├─ 组织架构 /basic-settings/organization
|
||||
-- ├─ 人员管理 /basic-settings/employee
|
||||
-- ├─ 职位管理 /basic-settings/position
|
||||
-- └─ 职级管理 /basic-settings/jobrank ← 本脚本新增
|
||||
--
|
||||
-- 对应页面:backend/src/views/basicSettings/jobRank/index.vue
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. views = [2](租户端),与同级的组织架构/人员管理/职位管理保持一致;
|
||||
-- platforms 留空(= 全端),移动端可通过 webview 容器打开同一页面。
|
||||
-- 2. 租户端角色(cid=2)的 rights 是显式菜单 ID 列表,菜单接口会按
|
||||
-- rights 过滤。只插菜单不授权,会出现「目录可见但页面被过滤」,
|
||||
-- 因此本脚本同时把菜单 ID 追加到角色 rights。
|
||||
-- ============================================================
|
||||
|
||||
SET @basic_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -28,7 +5,6 @@ SET @basic_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 职级管理(页面) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @basic_id, '职级管理', '/basic-settings/jobrank', '/basicSettings/jobRank/index.vue',
|
||||
@@ -44,9 +20,6 @@ SET @jobrank_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 角色授权:把菜单追加到所有租户端角色的 rights ----------
|
||||
-- 只处理 rights 非空(显式授权)的角色;rights 为空表示全权限,无需追加。
|
||||
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CAST(JSON_ARRAY_APPEND(CAST(rights AS JSON), '$', @jobrank_id) AS CHAR)
|
||||
WHERE cid = 2
|
||||
@@ -56,7 +29,6 @@ WHERE cid = 2
|
||||
AND @jobrank_id IS NOT NULL
|
||||
AND NOT JSON_CONTAINS(CAST(rights AS JSON), CAST(@jobrank_id AS JSON));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, views, platforms, type, sort
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path = '/basic-settings/jobrank';
|
||||
|
||||
@@ -1,27 +1,3 @@
|
||||
-- ============================================================
|
||||
-- OA 工作排班 —— 菜单配置(yz_system_menu)
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < oa_scheduling_menus.sql
|
||||
--
|
||||
-- 挂载位置:OA → 办公(个人办公),直接是页面,不再套「排班考勤」目录
|
||||
-- OA
|
||||
-- └─ 办公
|
||||
-- ├─ 工作排班(页面,/apps/oa/scheduling/board) ← 本脚本
|
||||
-- ├─ 考勤管理(页面,/apps/oa/attendance) ← oa_attendance_menus.sql
|
||||
-- └─ 考勤打卡(App,/apps/oa/attendance/clock) ← oa_attendance_menus.sql
|
||||
--
|
||||
-- 对应页面:backend/src/views/apps/oa/scheduling/index.vue
|
||||
-- 同一页面内完成:班次管理、排班方案(公司/部门/小组/指定员工)、
|
||||
-- 周看板、单个或批量员工的临时调配、变更记录查看。
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. 排班看板是 Web 管理端功能,platforms 显式为 ["web"],
|
||||
-- 移动端菜单不出现;
|
||||
-- 2. 历史版本创建的「排班考勤」目录不再使用,脚本会把它隐藏(保留数据);
|
||||
-- 3. 租户端角色(cid=2)的 rights 是显式菜单 ID 列表,菜单接口会按
|
||||
-- rights 过滤。只插菜单不授权,会出现「菜单存在但被过滤」,
|
||||
-- 因此本脚本同时把菜单 ID 追加到角色 rights。
|
||||
-- ============================================================
|
||||
|
||||
SET @oa_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -29,7 +5,6 @@ SET @oa_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- 「办公」目录:优先同名菜单,其次 /apps/oa/personal;都没有则回落 OA 根
|
||||
SET @office_id := (
|
||||
SELECT id FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
@@ -41,7 +16,6 @@ SET @office_id := (
|
||||
|
||||
SET @parent_id := IFNULL(@office_id, @oa_id);
|
||||
|
||||
-- ---------- 工作排班(页面,直接挂在办公下) ----------
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, platforms, type, creater, remark)
|
||||
SELECT @parent_id, '工作排班', '/apps/oa/scheduling/board', '/apps/oa/scheduling/index.vue',
|
||||
@@ -51,7 +25,6 @@ FROM DUAL
|
||||
WHERE @parent_id IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/apps/oa/scheduling/board' AND delete_time IS NULL) x);
|
||||
|
||||
-- 已存在则上移到「办公」,并纠正为 Web 页面
|
||||
UPDATE yz_system_menu
|
||||
SET pid = IFNULL(@parent_id, pid),
|
||||
sort = 88,
|
||||
@@ -60,8 +33,6 @@ SET pid = IFNULL(@parent_id, pid),
|
||||
is_visible = 1
|
||||
WHERE path = '/apps/oa/scheduling/board' AND delete_time IS NULL;
|
||||
|
||||
-- 历史的「排班考勤」目录:不再使用,隐藏(保留数据)
|
||||
-- 仅当目录下已无可见子菜单时才隐藏,避免误伤租户自行添加的子菜单
|
||||
UPDATE yz_system_menu
|
||||
SET is_visible = 0
|
||||
WHERE path = '/apps/oa/scheduling'
|
||||
@@ -80,8 +51,6 @@ SET @board_id := (
|
||||
LIMIT 1
|
||||
);
|
||||
|
||||
-- ---------- 角色授权:把菜单追加到所有租户端角色的 rights ----------
|
||||
-- 只处理 rights 非空(显式授权)的角色;rights 为空表示全权限,无需追加。
|
||||
UPDATE yz_system_admin_role
|
||||
SET rights = CAST(JSON_ARRAY_APPEND(CAST(rights AS JSON), '$', @board_id) AS CHAR)
|
||||
WHERE cid = 2
|
||||
@@ -91,7 +60,6 @@ WHERE cid = 2
|
||||
AND @board_id IS NOT NULL
|
||||
AND NOT JSON_CONTAINS(CAST(rights AS JSON), CAST(@board_id AS JSON));
|
||||
|
||||
-- ---------- 结果校验 ----------
|
||||
SELECT id, pid, title, path, component_path, platforms, type, sort, is_visible
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL
|
||||
|
||||
@@ -1,13 +1,3 @@
|
||||
-- ============================================================
|
||||
-- 审批流配置 —— 平台端菜单(yz_system_menu)
|
||||
-- 挂在「域名管理」目录(path = /system/domains)下,紧邻「域名审核」。
|
||||
-- 幂等脚本:按 path 判重,重复执行不会产生重复菜单。
|
||||
-- 执行:mysql -h <host> -P <port> -u <user> -p <db> < platform_approval_menu.sql
|
||||
-- ============================================================
|
||||
|
||||
-- 字段说明:
|
||||
-- type 1=目录 2=页面;views [1]=平台端;is_visible/status=1 显示并启用
|
||||
-- path 与 platform 前端静态路由 /system/approval 一致(component 同源,双保险)
|
||||
|
||||
SET @domain_dir := (
|
||||
SELECT id FROM yz_system_menu
|
||||
@@ -23,7 +13,6 @@ FROM DUAL
|
||||
WHERE @domain_dir IS NOT NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/system/approval' AND delete_time IS NULL) x);
|
||||
|
||||
-- 若未找到「域名管理」目录,则退化为平台端顶级菜单(pid=0)
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT 0, '审批流配置', '/system/approval', 'system/approval/index.vue',
|
||||
@@ -32,7 +21,6 @@ FROM DUAL
|
||||
WHERE @domain_dir IS NULL
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/system/approval' AND delete_time IS NULL) x);
|
||||
|
||||
-- 结果校验
|
||||
SELECT id, pid, title, path, component_path, views, type, is_visible, status
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path = '/system/approval';
|
||||
@@ -1,20 +1,4 @@
|
||||
-- ============================================================
|
||||
-- 排班模板 —— 平台端菜单(yz_system_menu)
|
||||
--
|
||||
-- 挂载位置:平台端「基础设置」(path = /basicSettings)下,与「字典管理」并列。
|
||||
-- 基础设置
|
||||
-- └─ 排班模板(页面,/basicSettings/schedTemplate)
|
||||
--
|
||||
-- 说明:
|
||||
-- 1. views = [1]:只在平台端出现;租户端通过 /backend/oa/scheduling/templates
|
||||
-- 读取模板(不在租户菜单里暴露模板管理入口)。
|
||||
-- 2. 平台端菜单接口(/platform/menu/:id)按 views 过滤,不按角色 rights 过滤,
|
||||
-- 因此本脚本无需追加角色授权。
|
||||
-- 3. 幂等:按 path 判重,重复执行不会产生重复菜单。
|
||||
-- 4. 本脚本不使用会话变量 / PREPARE,可整段执行也可逐条执行。
|
||||
-- ============================================================
|
||||
|
||||
-- 1) 有「基础设置」目录时,挂到该目录下
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT
|
||||
@@ -26,7 +10,6 @@ FROM DUAL
|
||||
WHERE EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL) b)
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/schedTemplate' AND delete_time IS NULL) e);
|
||||
|
||||
-- 2) 未找到「基础设置」目录时,退化为平台端顶级菜单(pid=0)
|
||||
INSERT INTO yz_system_menu
|
||||
(pid, title, path, component_path, icon, sort, status, is_visible, views, type, creater, remark)
|
||||
SELECT 0, '排班模板', '/basicSettings/schedTemplate', '/system/schedTemplate/index.vue',
|
||||
@@ -36,7 +19,6 @@ FROM DUAL
|
||||
WHERE NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings' AND delete_time IS NULL) b)
|
||||
AND NOT EXISTS (SELECT 1 FROM (SELECT id FROM yz_system_menu WHERE path = '/basicSettings/schedTemplate' AND delete_time IS NULL) e);
|
||||
|
||||
-- 结果校验:应返回 1 行
|
||||
SELECT id, pid, title, path, component_path, views, type, is_visible, status
|
||||
FROM yz_system_menu
|
||||
WHERE delete_time IS NULL AND path = '/basicSettings/schedTemplate';
|
||||
@@ -0,0 +1,70 @@
|
||||
|
||||
SET NAMES utf8mb4;
|
||||
|
||||
INSERT INTO `yz_backend_approval_flow`
|
||||
(`tid`, `module_code`, `biz_type`, `flow_code`, `apply_dept_ids`, `flow_name`,
|
||||
`description`, `is_default`, `status`, `is_deleted`)
|
||||
SELECT t.tid, 'oa', 'oa_attendance_fix', CONCAT('attendance_fix_', t.tid), '',
|
||||
'考勤补卡审批', '迟到/早退/缺卡补卡申请;审批通过后自动恢复正常打卡',
|
||||
1, 1, 0
|
||||
FROM (SELECT DISTINCT `tid` FROM `yz_backend_approval_flow` WHERE `is_deleted` = 0) t
|
||||
WHERE NOT EXISTS (
|
||||
SELECT 1 FROM `yz_backend_approval_flow` x
|
||||
WHERE x.`tid` = t.`tid` AND x.`biz_type` = 'oa_attendance_fix' AND x.`is_deleted` = 0
|
||||
);
|
||||
|
||||
INSERT INTO `yz_backend_approval_node`
|
||||
(`flow_id`, `tid`, `node_key`, `node_name`, `node_type`, `approver_type`, `approver_ids`,
|
||||
`multi_mode`, `allow_return`, `timeout_hours`, `prev_keys`, `next_keys`,
|
||||
`condition_expr`, `sort`, `is_deleted`)
|
||||
SELECT f.`id`, f.`tid`, 'start', '开始', 1, 1, '', 1, 0, 48, '', 'fix_approve', '', 1, 0
|
||||
FROM `yz_backend_approval_flow` f
|
||||
WHERE f.`biz_type` = 'oa_attendance_fix' AND f.`is_deleted` = 0
|
||||
AND NOT EXISTS (SELECT 1 FROM `yz_backend_approval_node` n WHERE n.`flow_id` = f.`id` AND n.`is_deleted` = 0);
|
||||
|
||||
INSERT INTO `yz_backend_approval_node`
|
||||
(`flow_id`, `tid`, `node_key`, `node_name`, `node_type`, `approver_type`, `approver_ids`,
|
||||
`multi_mode`, `allow_return`, `timeout_hours`, `prev_keys`, `next_keys`,
|
||||
`condition_expr`, `sort`, `is_deleted`)
|
||||
SELECT f.`id`, f.`tid`, 'fix_approve', '补卡审批', 2,
|
||||
COALESCE((
|
||||
SELECT n.`approver_type` FROM `yz_backend_approval_node` n
|
||||
JOIN `yz_backend_approval_flow` old ON old.`id` = n.`flow_id`
|
||||
WHERE old.`tid` = f.`tid` AND old.`is_deleted` = 0
|
||||
AND old.`biz_type` <> 'oa_attendance_fix'
|
||||
AND n.`node_type` = 2 AND n.`is_deleted` = 0 AND n.`approver_ids` <> ''
|
||||
ORDER BY n.`id` DESC LIMIT 1
|
||||
), 1),
|
||||
COALESCE((
|
||||
SELECT n.`approver_ids` FROM `yz_backend_approval_node` n
|
||||
JOIN `yz_backend_approval_flow` old ON old.`id` = n.`flow_id`
|
||||
WHERE old.`tid` = f.`tid` AND old.`is_deleted` = 0
|
||||
AND old.`biz_type` <> 'oa_attendance_fix'
|
||||
AND n.`node_type` = 2 AND n.`is_deleted` = 0 AND n.`approver_ids` <> ''
|
||||
ORDER BY n.`id` DESC LIMIT 1
|
||||
), ''),
|
||||
1, 0, 48, 'start', 'end', '', 2, 0
|
||||
FROM `yz_backend_approval_flow` f
|
||||
WHERE f.`biz_type` = 'oa_attendance_fix' AND f.`is_deleted` = 0
|
||||
AND NOT EXISTS (
|
||||
SELECT 1 FROM `yz_backend_approval_node` n
|
||||
WHERE n.`flow_id` = f.`id` AND n.`node_key` = 'fix_approve' AND n.`is_deleted` = 0
|
||||
);
|
||||
|
||||
INSERT INTO `yz_backend_approval_node`
|
||||
(`flow_id`, `tid`, `node_key`, `node_name`, `node_type`, `approver_type`, `approver_ids`,
|
||||
`multi_mode`, `allow_return`, `timeout_hours`, `prev_keys`, `next_keys`,
|
||||
`condition_expr`, `sort`, `is_deleted`)
|
||||
SELECT f.`id`, f.`tid`, 'end', '结束', 3, 1, '', 1, 0, 48, 'fix_approve', '', '', 3, 0
|
||||
FROM `yz_backend_approval_flow` f
|
||||
WHERE f.`biz_type` = 'oa_attendance_fix' AND f.`is_deleted` = 0
|
||||
AND NOT EXISTS (
|
||||
SELECT 1 FROM `yz_backend_approval_node` n
|
||||
WHERE n.`flow_id` = f.`id` AND n.`node_key` = 'end' AND n.`is_deleted` = 0
|
||||
);
|
||||
|
||||
SELECT f.`id`, f.`tid`, f.`flow_name`, f.`biz_type`, COUNT(n.`id`) AS node_count
|
||||
FROM `yz_backend_approval_flow` f
|
||||
LEFT JOIN `yz_backend_approval_node` n ON n.`flow_id` = f.`id` AND n.`is_deleted` = 0
|
||||
WHERE f.`biz_type` = 'oa_attendance_fix' AND f.`is_deleted` = 0
|
||||
GROUP BY f.`id`, f.`tid`, f.`flow_name`, f.`biz_type`;
|
||||
Reference in new issue
Block a user