Re: Many-to-one field in search

On Jul 22, 9:55 pm, Jonathan Hayward
<christos.jonathan.hayw...@gmail.com> wrote:
> Would it make sense to make
>
> A: A TextEmailField which does not have the ForeignKey, and
>
> B: A model which has the foreign key and a TextEmailField
>
> as a better and more standard approach?

Yes, that would make more sense. You could use an inline formset to
allow editing of multiple email addresses for each main record.
--
DR.

--
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.