Re: add a field to a form that isn't in a model

On Aug 2, 11:16 am, Shawn Milochik <sh...@milochik.com> wrote:
> Just add the fields to your ModelForm and then do whatever you want in
> your save() override.

Thanks for your reply, Shawn. Adding the fields in my ModelForm
doesn't seem to do the trick, by itself. The field doesn't appear in
the form unless I also add it to the model class, which necessitates
that I have a table field for the above mentioned model class X. The
upshot is that I would end up storing the same data in two different
tables. In my present case, that's no big problem, so perhaps I
shouldn't worry about it. But, just out of curiosity, I wonder what I
would do if I felt it was imperative to not store the data in two
different tables.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.