From ef42d74fea73b361b066f810b4550a9233dc24c1 Mon Sep 17 00:00:00 2001 From: Alejandro Rosales Date: Wed, 18 Feb 2026 09:20:54 -0600 Subject: [PATCH] fix: remove conversation_id update logic from cambios_plan trigger --- .../migrations/20260203204213_sincronizacion_con_remoto.sql | 6 ------ 1 file changed, 6 deletions(-) diff --git a/supabase/migrations/20260203204213_sincronizacion_con_remoto.sql b/supabase/migrations/20260203204213_sincronizacion_con_remoto.sql index 133a53f..f5a9caf 100644 --- a/supabase/migrations/20260203204213_sincronizacion_con_remoto.sql +++ b/supabase/migrations/20260203204213_sincronizacion_con_remoto.sql @@ -181,12 +181,6 @@ begin 'ACTUALIZACION'::public.tipo_cambio, 'tipo_origen', to_jsonb(old.tipo_origen), to_jsonb(new.tipo_origen), null); end if; - - if (new.conversation_id is distinct from old.conversation_id) then - insert into public.cambios_plan values (gen_random_uuid(), new.id, new.actualizado_por, now(), - 'ACTUALIZACION'::public.tipo_cambio, 'conversation_id', to_jsonb(old.conversation_id), to_jsonb(new.conversation_id), null); - end if; - -- 🔥 consumirlo para que NO se guarde en planes_estudio if v_response_id is not null then new.meta_origen := new.meta_origen - 'response_id';