mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-26 12:35:35 +02:00
c874bbc57b
main merged 123_issue_stage after this branch forked, so the branch's 123_channel_generalization now collides on the migration number. The runner keys schema_migrations by full version string and would still apply both, but a duplicate number is a merge hazard and convention violation, so move the channel migration to the next free slot (124). issue_stage (ALTER issue ADD COLUMN stage) and the channel generalization touch disjoint tables; verified on PG17 that 123_issue_stage applies cleanly on a DB already carrying 124_channel_generalization, so the two are order-independent. sqlc regenerated (v1.31.1): only the migration-number comment changed. MUL-3515 Co-authored-by: multica-agent <github@multica.ai>
11 lines
512 B
SQL
11 lines
512 B
SQL
-- Reverse 124_channel_generalization.up.sql. The lark_* tables were left
|
|
-- in place by the up migration, so rolling back only needs to drop the
|
|
-- channel_* tables that were added.
|
|
DROP TABLE IF EXISTS channel_binding_token;
|
|
DROP TABLE IF EXISTS channel_outbound_card_message;
|
|
DROP TABLE IF EXISTS channel_inbound_audit;
|
|
DROP TABLE IF EXISTS channel_inbound_message_dedup;
|
|
DROP TABLE IF EXISTS channel_chat_session_binding;
|
|
DROP TABLE IF EXISTS channel_user_binding;
|
|
DROP TABLE IF EXISTS channel_installation;
|