Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/zerver/migrations/0148_max_invites_forget_def...

23 lines
584 B
Python
Raw Normal View History

antispam: Make a setting for default Realm.max_invites. This makes this value much easier for a server admin to change than it was when embedded directly in the code. (Note this entire mechanism already only applies on a server open for anyone to create a realm.) Doing this also means getting the default out of the database. Instead, we make the column nullable, and when it's NULL in the database, treat that as whatever the current default is. This better matches anyway the likely model where there are a few realms with specially-set values, and everything else should be treated uniformly. The migration contains a `RenameField` step, which sounds scary operationally -- but it really does mean just the *field*, in the model within the Python code. The underlying column's name doesn't change.
2017-12-07 06:24:40 +01:00
# Generated by Django 1.11.6 on 2018-02-10 02:59
from django.db import migrations, models
class Migration(migrations.Migration):
dependencies = [
python: Normalize quotes with Black. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-02-12 08:20:45 +01:00
("zerver", "0147_realm_disallow_disposable_email_addresses"),
antispam: Make a setting for default Realm.max_invites. This makes this value much easier for a server admin to change than it was when embedded directly in the code. (Note this entire mechanism already only applies on a server open for anyone to create a realm.) Doing this also means getting the default out of the database. Instead, we make the column nullable, and when it's NULL in the database, treat that as whatever the current default is. This better matches anyway the likely model where there are a few realms with specially-set values, and everything else should be treated uniformly. The migration contains a `RenameField` step, which sounds scary operationally -- but it really does mean just the *field*, in the model within the Python code. The underlying column's name doesn't change.
2017-12-07 06:24:40 +01:00
]
operations = [
migrations.AlterField(
python: Normalize quotes with Black. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-02-12 08:20:45 +01:00
model_name="realm",
name="max_invites",
field=models.IntegerField(null=True, db_column="max_invites"),
antispam: Make a setting for default Realm.max_invites. This makes this value much easier for a server admin to change than it was when embedded directly in the code. (Note this entire mechanism already only applies on a server open for anyone to create a realm.) Doing this also means getting the default out of the database. Instead, we make the column nullable, and when it's NULL in the database, treat that as whatever the current default is. This better matches anyway the likely model where there are a few realms with specially-set values, and everything else should be treated uniformly. The migration contains a `RenameField` step, which sounds scary operationally -- but it really does mean just the *field*, in the model within the Python code. The underlying column's name doesn't change.
2017-12-07 06:24:40 +01:00
),
migrations.RenameField(
python: Normalize quotes with Black. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-02-12 08:20:45 +01:00
model_name="realm",
old_name="max_invites",
new_name="_max_invites",
antispam: Make a setting for default Realm.max_invites. This makes this value much easier for a server admin to change than it was when embedded directly in the code. (Note this entire mechanism already only applies on a server open for anyone to create a realm.) Doing this also means getting the default out of the database. Instead, we make the column nullable, and when it's NULL in the database, treat that as whatever the current default is. This better matches anyway the likely model where there are a few realms with specially-set values, and everything else should be treated uniformly. The migration contains a `RenameField` step, which sounds scary operationally -- but it really does mean just the *field*, in the model within the Python code. The underlying column's name doesn't change.
2017-12-07 06:24:40 +01:00
),
]