mirror of
https://github.com/zulip/zulip.git
synced 2025-11-23 07:52:35 +00:00
6bd34afa0d
This requires part 1 (which can take hours to run but generally doesn't require downtime) to be completed first. This portion of the migration will require the server to be completely down for a brief period; for chat.zulip.org with 250M UserMessage rows, it took about 60s to run; that time will vary depending on hardware details like whether the server has an SSD, but fundamentally shouldn't be long. Our upgrade-zulip and upgrade-zulip-from-git tools can apply this migration correctly; nothing special needs to be done. Fixes #13040.
26 lines
702 B
Python
26 lines
702 B
Python
# -*- coding: utf-8 -*-
|
|
# Generated by Django 1.11.23 on 2019-08-23 22:24
|
|
from __future__ import unicode_literals
|
|
|
|
from django.db import migrations, models
|
|
|
|
|
|
class Migration(migrations.Migration):
|
|
|
|
dependencies = [
|
|
('zerver', '0240_usermessage_migrate_bigint_id_into_id'),
|
|
]
|
|
|
|
operations = [
|
|
migrations.RunSQL("ALTER TABLE zerver_usermessage DROP COLUMN id_old;"),
|
|
migrations.RemoveField(
|
|
model_name='archivedusermessage',
|
|
name='bigint_id',
|
|
),
|
|
migrations.AlterField(
|
|
model_name='archivedusermessage',
|
|
name='id',
|
|
field=models.BigAutoField(primary_key=True, serialize=False),
|
|
),
|
|
]
|