Clarify implications of introducing new migrations
This commit is contained in:
parent
7413b787b6
commit
2e4893f4c1
1 changed files with 3 additions and 3 deletions
|
@ -5,9 +5,9 @@ const settings = require('../settings');
|
||||||
const { runMigrations } = require('./run_migrations');
|
const { runMigrations } = require('./run_migrations');
|
||||||
|
|
||||||
|
|
||||||
// NOTE: Add new migrations that need to traverse entire database, e.g. messages
|
// IMPORTANT: Add new migrations that need to traverse entire database, e.g.
|
||||||
// store, here. These will only run after attachment migration has completed in
|
// messages store, below. Whenever we need this, we need to force attachment
|
||||||
// the background:
|
// migration on startup:
|
||||||
const migrations = [
|
const migrations = [
|
||||||
// {
|
// {
|
||||||
// version: 0,
|
// version: 0,
|
||||||
|
|
Loading…
Reference in a new issue