yumoqing/integrated_crm_app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: ensure permission.permtype column is VARCHAR(255) after schema import

Browse Source
This commit is contained in:
yumoqing 2026-04-29 15:29:25 +08:00
parent d5c0fcb1cd
commit c967cfffda
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
build.sh
View File

@ -183,6 +183,12 @@ echo " Database '$DB_NAME' created."
mysql -h "$DB_HOST" -P "$DB_PORT" -u "$DB_USER" -p"$DB_PASS" "$DB_NAME" < "$APP_DIR/integrated_crm_app_schema.sql" mysql -h "$DB_HOST" -P "$DB_PORT" -u "$DB_USER" -p"$DB_PASS" "$DB_NAME" < "$APP_DIR/integrated_crm_app_schema.sql"
echo " Schema imported." echo " Schema imported."
# Fix permission table column lengths (rbac xlsx may define shorter lengths)
mysql -h "$DB_HOST" -P "$DB_PORT" -u "$DB_USER" -p"$DB_PASS" "$DB_NAME" <<EOSQL
ALTER TABLE permission MODIFY COLUMN permtype VARCHAR(255) COMMENT '权限类型';
EOSQL
echo " Permission table columns fixed."
# Generate config.json with encrypted password # Generate config.json with encrypted password
python3 <<PYEOF python3 <<PYEOF
import sys, json import sys, json