Hello, let's assume we have a model for photos with the fields id, user, photo. Any user should be able to categorize his foto with a given number of categories, e.g. person, car, building. In future it's possible that I add more categories.
My question is whether the new category field should be a ChoiceField, or a ForeignKey? I would prefer a ChoiceField because - I am 99% sure that there won't be new categories. - the only person who maybe adds a new category will be me. - another model would bloat up my database and my models.py But maybe I should use a ForeignKey because, - I don't have to edit the model/table. - it's easier to add a choice to a table than in the source code. - because values in databases should be atomic. Otherwise, assuming that syncdb can't handle adding new choices to an existing table, adding a choice directly in the database application (MySQL, PostgreSQL) is no problem. Removing a choice won't happen. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
