Temporarily disable post-attachment migration migrations

This commit is contained in:
Daniel Gasienica 2018-04-02 15:26:23 -04:00
parent d9be6a0f94
commit bfbeedab5c
4 changed files with 27 additions and 27 deletions

View file

@ -8,7 +8,7 @@ const { runMigrations } = require('./run_migrations');
// any expensive operations, e.g. modifying all messages / attachments, etc., as
// it may cause out-of-memory errors for users with long histories:
// https://github.com/signalapp/Signal-Desktop/issues/2163
const migrations = [
exports.migrations = [
{
version: '12.0',
migrate(transaction, next) {
@ -144,7 +144,7 @@ const migrations = [
const database = {
id: 'signal',
nolog: true,
migrations,
migrations: exports.migrations,
};
exports.run = ({ Backbone } = {}) =>
@ -152,5 +152,5 @@ exports.run = ({ Backbone } = {}) =>
exports.getDatabase = () => ({
name: database.id,
version: last(migrations).version,
version: last(exports.migrations).version,
});

View file

@ -2,14 +2,14 @@ const { runMigrations } = require('./run_migrations');
exports.migrations = [
{
version: 18,
async migrate(transaction, next) {
console.log('Migration 18');
console.log('Attachments stored on disk');
next();
},
},
// {
// version: 18,
// async migrate(transaction, next) {
// console.log('Migration 18');
// console.log('Attachments stored on disk');
// next();
// },
// },
];
exports.run = runMigrations;