For something like categories, I would go with a separate model and use ForeignKey. For that 1% chance when you have to add a new category, it will be a lot easier. Plus, what if requirements change in the future and you are adding/deleting categories more than you anticipated?
Using choices with a char/integer field is good for lists of options that will *never* change... gender (M,F), age ranges (0-18,19-25,etc), statuses (published,draft). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
