Files
MoFin/scripts/test_db_write.py
T
hmo efdfaf956a fix(price_events): unify event storage to DB (dual-write + backfill)
User caught the inconsistency: system claims DB-first but price events
only went to price_events.json, leaving DB table stale since Jul 6.

Root cause chain found:
- record_event() only wrote JSON, never called mofin_db.write_price_event
- price_events.code has FK -> stocks(code); events for unregistered stocks
  (new candidates, HK) silently failed INSERT and were lost to DB
- mofin_db.write_price_event swallows errors (returns False silently)

Fixes:
- record_event now dual-writes: DB (authoritative) + JSON (compat for
  legacy readers mo_config/strategy_feedback/system_health_check)
- auto-registers unknown codes into stocks table before event insert
- one-time backfill: 4064 JSON events -> DB (total 6353 rows, last=today)
- verified: record_event TEST99 lands in both DB and JSON
2026-07-20 17:46:57 +08:00

15 lines
602 B
Python

import sys
sys.path.insert(0, '/home/hmo/.hermes/profiles/position-analyst/scripts')
sys.path.insert(0, '/home/hmo/MoFin')
from mofin_db import get_conn, write_price_event
c = get_conn()
ok = write_price_event(c, code='TEST99', name='测试股', event_type='entry_zone',
price=12.34, trigger_value='12.0~12.5', event_label='加仓区间')
print('write_price_event returned:', ok)
r = c.execute("SELECT code,created_at FROM price_events WHERE code='TEST99'").fetchone()
print('row:', r)
c.execute("DELETE FROM price_events WHERE code='TEST99'")
c.commit()
c.close()
print('done')