From 5f844fd3f2b35075bd3a90c71315c321fec6a6e8 Mon Sep 17 00:00:00 2001 From: lain Date: Mon, 4 Nov 2019 15:38:28 +0100 Subject: [PATCH] Migrations: Add a fixup migration for the muted_notifications This sets info->muted_notifications to an emtpy array if it is explicitly set to null before. This can happen when safe_jsonb_set coalesces to a jsonb null, which will make ecto not use the default value of [] anymore because it has been explicitly overwritten. --- .../20191104143558_fix_null_muted_notification_fields.exs | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 priv/repo/migrations/20191104143558_fix_null_muted_notification_fields.exs diff --git a/priv/repo/migrations/20191104143558_fix_null_muted_notification_fields.exs b/priv/repo/migrations/20191104143558_fix_null_muted_notification_fields.exs new file mode 100644 index 000000000..e17e75983 --- /dev/null +++ b/priv/repo/migrations/20191104143558_fix_null_muted_notification_fields.exs @@ -0,0 +1,7 @@ +defmodule Pleroma.Repo.Migrations.FixNullMutedNotificationFields do + use Ecto.Migration + + def change do + execute("update users set info = safe_jsonb_set(info, '{muted_notifications}', '[]'::jsonb, true) where local = true and info->'muted_notifications' = 'null'::jsonb") + end +end -- 2.45.2