fix: 修复模型管理"参与官方同步"与"状态"开关无法保存的问题

[wans10]

问题描述

模型管理模块中，创建或编辑模型时，将"参与官方同步"或"状态"开关关闭后保存，刷新页面后开关仍显示为开启状态。

根本原因

1. Insert 方法问题

当使用 DB.Create(mi) 创建模型时，GORM 会因为 default:1 标签将零值字段（status=0, sync_official=0）替换为默认值 1，并回写到结构体。后续的更新操作使用的是已被覆盖的值。

2. Update 方法问题

原始代码使用 Updates(mi) 更新模型，但 GORM 的 Updates() 方法默认忽略零值字段，导致 status=0 和 sync_official=0 不会被写入数据库。

解决方案

Insert 方法

在调用 DB.Create() 之前保存 status 和 sync_official 的原始值，创建后使用保存的原始值进行二次更新。

Update 方法

使用 GORM 的 Select() 方法显式指定要更新的字段，强制更新包括零值在内的所有字段。

修改文件

• model/model_meta.go
  • Insert(): 保存原始值后再更新
  • Update(): 使用 Select() 指定更新字段

测试验证

1. 创建新模型时关闭两个开关 → 保存后刷新页面，确认开关保持关闭状态 ✅
2. 编辑现有模型，将开关从开启切换为关闭 → 保存后刷新页面，确认状态正确 ✅
3. 反向测试：将开关从关闭切换为开启 → 保存后刷新页面，确认状态正确 ✅

Summary by CodeRabbit

• Bug Fixes
  • Fixed an issue where zero-value data was not being preserved correctly when creating and updating records. Records now properly retain default values and empty field states during save operations.

[coderabbitai]

Walkthrough

The model_meta.go file's Insert and Update methods were refactored to handle GORM defaults and zero-values more precisely. Insert now uses a create-then-update sequence to preserve original Status and SyncOfficial values. Update switches from session-based controls to a direct Model update with explicit field selection.

Changes

Cohort / File(s)	Summary
Data Persistence Logic model/model_meta.go	Insert method changed from single-create to create-then-update flow to preserve zero-value Status and SyncOfficial fields. Update method replaced session-based approach with direct Model update specifying explicit field list (model_name, description, icon, tags, vendor_id, endpoints, status, sync_official, name_rule, updated_time) via targeted Select for zero-value inclusion.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A hop, skip, and update in the database store,
Where zeros are treasured and defaults adore,
Insert then refine—oh what clever design!
Fields preserved with precision so fine,
Status and sync in their rightful place! 🎯

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is in Chinese and refers to fixing an issue with model management where 'Official Sync' and 'Status' switches fail to save properly. This directly matches the PR objectives which document this exact problem and its solution.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}