Fix null field issues exposed by Django 1.1.2

Apparently Django 1.1.1 let null fields pass right through but this now
causes reporead to blow up in 1.1.2. Fix the issue and get things working
again by allowing nulls where it probably makes sense and including a
migration to fix the issue, which for the real database will be a no-op.

Signed-off-by: Dan McGee <dan@archlinux.org>

1 files changed, 3 insertions, 3 deletions

diff --git a/main/models.py b/main/models.py
index 1f938cc..52e6895 100644
--- a/main/models.py
+++ b/main/models.py
@@ -160,14 +160,14 @@ class Package(models.Model):
     pkgbase = models.CharField(max_length=255, db_index=True)
     pkgver = models.CharField(max_length=255)
     pkgrel = models.CharField(max_length=255)
-    pkgdesc = models.CharField(max_length=255)
-    url = models.CharField(max_length=255)
+    pkgdesc = models.CharField(max_length=255, null=True)
+    url = models.CharField(max_length=255, null=True)
     compressed_size = models.PositiveIntegerField(null=True)
     installed_size = models.PositiveIntegerField(null=True)
     build_date = models.DateTimeField(null=True)
     last_update = models.DateTimeField(null=True, blank=True)
     files_last_update = models.DateTimeField(null=True, blank=True)
-    license = models.CharField(max_length=255)
+    license = models.CharField(max_length=255, null=True)
     objects = PackageManager()
     class Meta:
         db_table = 'packages'