From aed7ef0caeb92d92eab9223663e2fe781f00d5fa Mon Sep 17 00:00:00 2001
From: Daniel Lockyer <hi@daniellockyer.com>
Date: Mon, 9 May 2022 16:49:28 +0100
Subject: [PATCH] Altered wording in migration utils

- if the table doesn't exist, it's not necessarily a failure that we
  should be informing the user about
- this brings the message wording in line with other log lines of
  similar operations
---
 core/server/data/migrations/utils.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/server/data/migrations/utils.js b/core/server/data/migrations/utils.js
index 052b1243d3..734352eb36 100644
--- a/core/server/data/migrations/utils.js
+++ b/core/server/data/migrations/utils.js
@@ -56,7 +56,7 @@ function dropTables(names) {
                 const exists = await connection.schema.hasTable(name);
 
                 if (!exists) {
-                    logging.warn(`Failed to drop table: ${name} - table does not exist`);
+                    logging.warn(`Skipping dropping table: ${name} - table does not exist`);
                 } else {
                     logging.info(`Dropping table: ${name}`);
                     await commands.deleteTable(name, connection);
@@ -80,7 +80,7 @@ function recreateTable(name, tableSpec) {
             const exists = await connection.schema.hasTable(name);
 
             if (!exists) {
-                logging.warn(`Failed to drop table: ${name} - table does not exist`);
+                logging.warn(`Skipping dropping table: ${name} - table does not exist`);
             } else {
                 logging.info(`Dropping table: ${name}`);
                 await commands.deleteTable(name, connection);