Repository navigation
Conversation
vido.broadcasts holds one row per campaign: its fingerprint and the photo's Telegram file id once uploaded. vido.broadcast_deliveries holds one row per destination chat with the localized message, lease, retry state, Telegram evidence and an outcome saying why the chat was or was not reached, which is what Vido's broadcast report counts. Same delivery contract as 007, with two differences. chat_id is a bare id with a sign check instead of a foreign key, because private chats last seen before July 2026 have no core.chat row. The outcome checks spell out IS NOT NULL, since a NULL inside IN (...) makes a CHECK pass; the contract test covers both statuses without an outcome. vido_core can select, insert and update, never delete. The changelog entry for 014 already landed with 015; this adds the operator line for applying it, including by hand on vido_test. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Member
Author
|
Migration 014 landed on dev as 0130b67, identical to this branch; dev also carries 016 and the updated operator note. Closing as superseded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the outbox Vido's new broadcast tool writes to (FreshLabDev/vido, branch
feat/broadcast).vido.broadcasts: one row per campaign, its fingerprint and the photo's Telegram file id once uploaded.vido.broadcast_deliveries: one row per destination chat with the localized message, lease, retry state, Telegram evidence andoutcome(delivered,text_only,blocked,deactivated,not_started,removed,no_rights,not_found).Same delivery contract as
007, two differences:chat_idis not a foreign key. Private chats last seen before July 2026 were recorded with presencechat_id0 and have nocore.chatrow; a sign check keeps private and group ids apart instead.IS NOT NULL. A NULL insideIN (...)makes the whole CHECK NULL, which PostgreSQL accepts; the first draft let anunreachablerow without an outcome through, and the contract test now covers both statuses.vido_coregets SELECT, INSERT, UPDATE, no DELETE. The changelog entry for014already landed with015(4fbdbd8); this adds the operator line, including applying it by hand onvido_test.Tested: all 15 migrations twice and every contract test on a local PostgreSQL 17 cluster with
bin/apply.sh(Docker is not available on this machine, so not throughbin/test.shitself). Not applied anywhere.