Re: Many-to-one field in search

2010-07-23 Thread Jonathan Hayward
Thank you! On Fri, Jul 23, 2010 at 1:44 AM, Daniel Roseman wrote: > On Jul 22, 9:55 pm, Jonathan Hayward > 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 bet

Re: Many-to-one field in search

2010-07-22 Thread Daniel Roseman
On Jul 22, 9:55 pm, Jonathan Hayward 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 inl

Re: Many-to-one field in search

2010-07-22 Thread Jonathan Hayward
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? On Thu, Jul 22, 2010 at 3:13 PM, Jonathan Hayward < christos.jonathan.hayw...@gmail.com> wrote: > I am tryin

Many-to-one field in search

2010-07-22 Thread Jonathan Hayward
I am trying to make an EmailField variant which: 1: Is based on TEXT rather than VARCHAR, and 2: May be in a many-to-one relationship with entity. I presently have: class TextEmailField(models.EmailField): entity = models.ForeignKey(Entity) def __init__(self, *arguments, **keywords):