summaryrefslogtreecommitdiff
path: root/news
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2011-03-29 17:39:59 -0500
committerDan McGee <dan@archlinux.org>2011-04-07 17:04:00 -0500
commit6fe08cd68901e698f4a0741e177354a45c753b46 (patch)
tree28a464e34823b62a1fcf5b26b02174b477ec10be /news
parentac550af4c9b31fe85b783d846adad75bb7d4aa02 (diff)
Utilize Django 1.3 'on_delete' feature on several foreign keys
The most important one here is PROTECT to keep people from making bone-headed plays and deleting an Arch or Repo and every package along with it. We can use this in a few other places, as well as some carefully placed SET_NULL indicators. Note that nothing here pushes deletion responsibilities down to the database, although that will probably happen in a future commit. Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'news')
-rw-r--r--news/models.py3
1 files changed, 2 insertions, 1 deletions
diff --git a/news/models.py b/news/models.py
index 5e467515..33d958e0 100644
--- a/news/models.py
+++ b/news/models.py
@@ -6,7 +6,8 @@ from django.contrib.sites.models import Site
class News(models.Model):
slug = models.SlugField(max_length=255, unique=True)
- author = models.ForeignKey(User, related_name='news_author')
+ author = models.ForeignKey(User, related_name='news_author',
+ on_delete=models.PROTECT)
postdate = models.DateTimeField("post date", db_index=True)
last_modified = models.DateTimeField(editable=False, db_index=True)
title = models.CharField(max_length=255)