feat(usable): integrate current dbtool implementation snapshot
Some checks failed
release-smoke / macos-13 / x86_64-apple-darwin (push) Has been cancelled
release-smoke / ubuntu-latest / x86_64-unknown-linux-gnu (push) Has been cancelled
release-smoke / windows-latest / x86_64-pc-windows-msvc (push) Has been cancelled

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Paperclip CTO
2026-04-02 08:26:18 +00:00
parent a28dab4cd9
commit d5f69462b0
73 changed files with 5895 additions and 322 deletions

View File

@@ -27,6 +27,12 @@ These assets give backend, frontend, and QA one small shared dataset for Postgre
- `examples/fixtures/mysql/init.sql` 会显式授予 `dbtool` 用户对 `qa_demo` 的权限
- 这样可避免 demo 容器默认库名与 QA 目标库名不一致时,`dbtool` 无法访问 `qa_demo`
## PostgreSQL Bootstrap Note
- `docker-compose.demo.yml``scripts/tui/demo-stack.sh` 现在保留 `postgres` 作为 demo 超级用户,密码为 `dbtoolroot`
- `examples/fixtures/postgres/init.sql` 会把 `dbtool` 收敛为 `NOSUPERUSER` 的 app 用户,并只授予 `dbtool_demo.qa_demo` 的读权限
- 若容器是在旧配置(`POSTGRES_USER=dbtool`)下初始化的,需要先 `docker compose -f docker-compose.demo.yml down -v``scripts/tui/demo-stack.sh reset` 再重建,否则旧卷里的超级权限不会自动消失
## SQLite Bootstrap Note
- `examples/scripts/bootstrap-sqlite.sh` 现支持 `sqlite3``node:sqlite``python3 sqlite3` 三种 seed 路径