Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions app/database/migrations/026_normalize_outcomes_to_uppercase.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
-- Migration 026: Normalize lead_call_tracker.outcome values to UPPERCASE.
-- All Clairvoyance code uses UPPERCASE outcome literals; this backfills any
-- historical rows where a bypass path may have written lowercase.
-- Going forward, the DB query layer enforces UPPER() at INSERT/UPDATE time.

BEGIN;

UPDATE lead_call_tracker
SET outcome = UPPER(outcome)
WHERE outcome IS NOT NULL
AND outcome <> UPPER(outcome);

COMMIT;
4 changes: 2 additions & 2 deletions app/database/queries/breeze_buddy/lead_call_tracker.py
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ def insert_lead_call_tracker_query(
call_id,
outbound_number_id,
call_direction.value,
outcome,
outcome.upper() if outcome else None,
datetime.now(),
datetime.now(),
]
Expand Down Expand Up @@ -330,7 +330,7 @@ def update_lead_call_completion_details_query(
set_clauses.append(f'"status" = ${len(values)}')

if outcome is not None:
values.append(outcome)
values.append(outcome.upper())
set_clauses.append(f'"outcome" = ${len(values)}')

if meta_data is not None:
Expand Down
Loading