On Wed, Apr 9, 2008 at 2:56 PM, ydjango <[EMAIL PROTECTED]> wrote: > Not for model form, if a ChoiceField is based on foreign Key. It is > getting values from the referenced table using the __unicode__ method > in that table and ignoring the choices field passed to it.
Not in this case; the moment you change any aspect of the definition of a field in a ModelForm, you're 100% on your own for that field. This means that if you change any aspect of the definition of a choice-based field in a ModelForm, you're on the hook for all its other required attributes, including choices. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
