From 2e4893f4c138b08e268014cef6132e5bf4e893f9 Mon Sep 17 00:00:00 2001 From: Daniel Gasienica Date: Mon, 2 Apr 2018 18:54:50 -0400 Subject: [PATCH] Clarify implications of introducing new migrations --- .../migrations_1_database_without_attachment_data.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/js/modules/migrations/migrations_1_database_without_attachment_data.js b/js/modules/migrations/migrations_1_database_without_attachment_data.js index 025b6a2e9..fd1feeb17 100644 --- a/js/modules/migrations/migrations_1_database_without_attachment_data.js +++ b/js/modules/migrations/migrations_1_database_without_attachment_data.js @@ -5,9 +5,9 @@ const settings = require('../settings'); const { runMigrations } = require('./run_migrations'); -// NOTE: Add new migrations that need to traverse entire database, e.g. messages -// store, here. These will only run after attachment migration has completed in -// the background: +// IMPORTANT: Add new migrations that need to traverse entire database, e.g. +// messages store, below. Whenever we need this, we need to force attachment +// migration on startup: const migrations = [ // { // version: 0,