Why: user create/reset-password and conversation flag updates wrote 1/0
literals and boolInt ints into BOOLEAN columns; SQLite tolerates it,
PostgreSQL rejects with 42804. The 10-04 user create on pg1 failed midway
(empty password_hash, is_admin=f), and password reset, user list (bool
scanned into int) and login (GetUserAuthState scan) were all broken on
the postgres tier.
Evidence: store tests green; against the live pg1 the fixed CLI completes
user reset-password and user list (isAdmin=true, mustChangePassword=true,
hasPassword=true).
Impact: auth/account management and conversation list/flag paths work on
postgres; SQLite unchanged (0/1 converts via driver.Bool). No schema
changes.
Refs: dev-repo PR for gitlink bump (feature/store-pg-bool-dialect)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
PG 档下布尔列被写成 1/0 字面量与 boolInt 整数参数(SQLite 容忍、PG 报 42804):10-04 的 user create 在 pg1 半失败(空 password_hash、is_admin=f),password reset / user list(bool 扫进 int)/ 登录(GetUserAuthState 扫描)在 PG 档全部不可用。
What
Evidence
Impact
PG 档的账号管理与会话标记/列表路径恢复可用;SQLite 行为不变;无 schema 变更。
Refs
Dev 仓 gitlink bump PR(同名分支)
0cb7e97a20to14aa60b698