Files
ten31-database/backend/migrations/0006_reminders.down.sql
T
Keysat f181525926 Add reminders & follow-ups (W1) (v0.1.0:92)
First-class reminders tied to the fundraising grid — foundation of the agreed
reminders -> NL-search -> bot-mutations plan (keep LP data off third-party LLMs).

- reminders table (migration 0006; logical FK to fundraising_investors.id +
  denormalized name), CRUD at /api/reminders (soft-delete; open/done/snoozed/
  cancelled; assignee; source; source_row_id resolution)
- read-only derived reminder_status grid column (overdue/due_soon/open),
  filterable; orphan reconciler cancels reminders when an investor leaves the grid
- Reminders page, Dashboard "Reminders Due" card, daily-digest reminders section
- per-investor last_activity_at recency rollup (shared block for the W2 NL query)
- tests: test_reminders.py + digest reminders test (31/31 green, render-smoke green)
2026-06-18 14:45:46 -05:00

9 lines
444 B
SQL

-- Manual rollback for 0006_reminders.sql (never auto-applied).
-- Drops the whole reminders feature table. Per the never-hard-delete guardrail this
-- discards reminder history, so only run it to reverse a bad migration on a dev/copy DB.
DROP INDEX IF EXISTS idx_reminders_assignee;
DROP INDEX IF EXISTS idx_reminders_due;
DROP INDEX IF EXISTS idx_reminders_status;
DROP INDEX IF EXISTS idx_reminders_investor;
DROP TABLE IF EXISTS reminders;