feat(dictionary): commit the hnc_lemma_words_<N> columns (missing dependency of #70/#72) #74
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
project-halkyon/halkyon-infra!74
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/74/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The 47
hnc_lemma_words_500 … 23500boolean columns were applied to the live DB out-of-band and never committed. But #70 (repairadd_dictionary_vocabulary, already merged) filters on them 21×, and #72 (frequency-ordering, open) does too. Somain's migration tree is currently inconsistent — a from-scratchsupabase db resetfails withcolumn "hnc_lemma_words_500" does not exist.What
Commits
202606291355_add_hnc_lemma_words_bulks.sql(the creating migration). Its timestamp sorts before the20260701…RPC migrations, so on reset the columns exist before #70/#72 reference them — the tree becomes consistent again. No effect on the live DB (columns already there).Merge order
Merge this before/with #72. After this + #72 + #73, the tree is: … →
202606291355(columns) → #70 (repair) → #71 (hnc_rank) → #72 (ordering) → #73 (drop stray cols).Note: the two divergent migrations (
20260628120000,202606291840) that rewrote the RPC against a non-existent schema are intentionally not committed — #70 supersedes them.