mirror of
https://gh-proxy.org/https://github.com/klinsmaya/multica.git
synced 2026-11-09 09:56:47 +08:00
67c6aa05c4
* feat(telegram): add Telegram channel integration Co-authored-by: multica-agent <[email protected]> * chore(telegram): rebase onto main and renumber migrations to 366-367 349/350 collided with main's agent_task_queue_chat_terminal_resume_index and agent_task_queue_chat_retired_session_index. Renumber the Telegram origin pair to the next free prefixes, update the cross-references inside the SQL comments, and point telegram_origin_migration_test.go at the new filenames. Contributor-facing behavior is unchanged. Co-authored-by: multica-agent <[email protected]> --------- Co-authored-by: multica-agent <[email protected]> Co-authored-by: Bohan-J <[email protected]>
12 lines
719 B
SQL
12 lines
719 B
SQL
-- Extend issue.origin_type for issues created by the Telegram `/issue`
|
|
-- command. origin_id stores the chat_session id, matching the existing Lark,
|
|
-- Slack, DingTalk, and WeCom channel origins.
|
|
--
|
|
-- This only widens the allowed set. Recreate the CHECK as NOT VALID so the
|
|
-- ACCESS EXCLUSIVE lock is held briefly; migration 367 performs the table scan
|
|
-- under SHARE UPDATE EXCLUSIVE without blocking normal reads and writes.
|
|
ALTER TABLE issue DROP CONSTRAINT IF EXISTS issue_origin_type_check;
|
|
ALTER TABLE issue ADD CONSTRAINT issue_origin_type_check
|
|
CHECK (origin_type IN ('autopilot', 'quick_create', 'lark_chat', 'slack_chat', 'agent_create', 'dingtalk_chat', 'wecom_chat', 'telegram_chat'))
|
|
NOT VALID;
|