Tom, the problem is not caused by using `exclude`, it is caused by not using `fields`. If you use `exclude` or simply don't specify `exclude` or `fields` then all fields will be included. Thanks for your other example and description of the problem, I just wanted to clarify that it is not only a problem when using `exclude`.
Cheers. Tai. On Jan 12, 2:40 am, Tom Evans <tevans...@googlemail.com> wrote: > Are there any other situations where this can happen? The problem is > in fact caused by using 'exclude' to choose the fields presented in a > model form, using 'fields' and explicitly listing the fields seems > much safer. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
