mirror of
https://github.com/bookwyrm-social/bookwyrm.git
synced 2024-06-26 08:50:39 +00:00
ed83032330
If the database has multiple users with an empty email column, this migration will fail because multiple empty strings break the unique constraint. A fresh database won't have this problem because it won't have any legacy users with empty strings instead of NULL, but for existing databases we need to convert the empty strings to NULL so they don't run awry of the unique constraint.
38 lines
1.1 KiB
Python
38 lines
1.1 KiB
Python
# Generated by Django 3.0.7 on 2021-01-18 19:54
|
|
|
|
from django.db import migrations, models
|
|
|
|
def empty_to_null(apps, schema_editor):
|
|
User = apps.get_model("bookwyrm", "User")
|
|
db_alias = schema_editor.connection.alias
|
|
User.objects.using(db_alias).filter(email="").update(email=None)
|
|
|
|
def null_to_empty(apps, schema_editor):
|
|
User = apps.get_model("bookwyrm", "User")
|
|
db_alias = schema_editor.connection.alias
|
|
User.objects.using(db_alias).filter(email=None).update(email="")
|
|
|
|
class Migration(migrations.Migration):
|
|
|
|
dependencies = [
|
|
('bookwyrm', '0036_annualgoal'),
|
|
]
|
|
|
|
operations = [
|
|
migrations.AlterModelOptions(
|
|
name='shelfbook',
|
|
options={'ordering': ('-created_date',)},
|
|
),
|
|
migrations.AlterField(
|
|
model_name='user',
|
|
name='email',
|
|
field=models.EmailField(max_length=254, null=True),
|
|
),
|
|
migrations.RunPython(empty_to_null, null_to_empty),
|
|
migrations.AlterField(
|
|
model_name='user',
|
|
name='email',
|
|
field=models.EmailField(max_length=254, null=True, unique=True),
|
|
),
|
|
]
|