From 72e80817a5e5b2db0e61ce7b2a34dd321757f434 Mon Sep 17 00:00:00 2001 From: Maximilian Friedersdorff Date: Fri, 8 Jul 2022 21:49:42 +0100 Subject: [PATCH] Fix null=True vs blank=True on string fields Django documentation suggests no using null=True, but instead defaulting to the empty string. It's necessary of course to allow blank=True so that users don't have to enter the field --- .../0003_alter_post_body_alter_post_title.py | 23 +++++++++++++++++++ flangr/posts/models.py | 4 ++-- 2 files changed, 25 insertions(+), 2 deletions(-) create mode 100644 flangr/posts/migrations/0003_alter_post_body_alter_post_title.py diff --git a/flangr/posts/migrations/0003_alter_post_body_alter_post_title.py b/flangr/posts/migrations/0003_alter_post_body_alter_post_title.py new file mode 100644 index 0000000..64da38b --- /dev/null +++ b/flangr/posts/migrations/0003_alter_post_body_alter_post_title.py @@ -0,0 +1,23 @@ +# Generated by Django 4.0.5 on 2022-07-08 20:49 + +from django.db import migrations, models + + +class Migration(migrations.Migration): + + dependencies = [ + ("posts", "0002_alter_comment_post_alter_post_img"), + ] + + operations = [ + migrations.AlterField( + model_name="post", + name="body", + field=models.TextField(blank=True, default=""), + ), + migrations.AlterField( + model_name="post", + name="title", + field=models.CharField(blank=True, default="", max_length=255), + ), + ] diff --git a/flangr/posts/models.py b/flangr/posts/models.py index fa22ba2..ad1786e 100644 --- a/flangr/posts/models.py +++ b/flangr/posts/models.py @@ -17,8 +17,8 @@ class Post(models.Model): posted = models.DateTimeField(auto_now_add=True) public = models.BooleanField(default=False) - title = models.CharField(max_length=255, null=True) - body = models.TextField(null=True) + title = models.CharField(max_length=255, blank=True, default="") + body = models.TextField(blank=True, default="") user = models.ForeignKey(settings.AUTH_USER_MODEL, on_delete=models.CASCADE)