`gjnRdZddlmZddlZddlZddZej ddZy)uShared SQLite primitives for the small per-profile / board stores. The projects and kanban stores open WAL SQLite files with the same two primitives — an idempotent column-add migration and an IMMEDIATE write transaction. One definition here keeps the two stores from drifting. ) annotationsNc |jd|d|y#tj$r&}dt|j vrYd}~yd}~wwxYw)aP``ALTER TABLE ADD COLUMN ``, idempotent across races. Returns ``True`` when this call added the column. Swallows the ``duplicate column name`` error a concurrent migrator may have run first (issue #21708). ``column`` is the human-readable name for the call site; ``ddl`` carries the actual definition. z ALTER TABLE z ADD COLUMN Tzduplicate column nameNF)executesqlite3OperationalErrorstrlower)conntablecolumnddlexcs I/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/sqlite_util.pyadd_column_if_missingrsR |E7,se<=  # # "c#hnn&6 6 sAA AAc#K|jd ||jdy#t$r- |jd#tj$rYwxYwwxYww)aAn IMMEDIATE write transaction: at most one concurrent writer wins. The explicit ROLLBACK is guarded so a SQLite auto-rollback (no active transaction left under EIO / lock contention / corruption) cannot shadow the original exception with a spurious rollback error. zBEGIN IMMEDIATECOMMITROLLBACKN)r Exceptionrr)r s r write_txnrsp LL"#   X   LL $ ''    s<A$+A$ A!AA!AA!AA!!A$) r sqlite3.Connectionr rr rr rreturnbool)r r)__doc__ __future__r contextlibrrcontextmanagerrrrs4#" r