@Melvyn Thank you. It actually worked out as you said. It needed a redesign.
On Wed, Aug 22, 2012 at 1:44 PM, Sithembewena Lloyd Dube <[email protected]>wrote: > @Melvyn, thanks - that makes sense. > > > On Wed, Aug 22, 2012 at 3:18 AM, Melvyn Sopacua <[email protected]>wrote: > >> On 22-8-2012 3:04, Sithembewena Lloyd Dube wrote: >> >> > I found your response to the OP interesting, yet I cannot quite follow >> it. >> > Even if he sets a unique attribute (presumably Boolean/ Checkbox?) >> >> Nope, this unique attribute: >> <https://docs.djangoproject.com/en/1.4//ref/models/fields/#unique> >> >> By design, the foreign key will now not contain duplicates so distinct >> is no longer necessary. >> -- >> Melvyn Sopacua >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to [email protected]. >> 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. >> >> > > > -- > Regards, > Sithembewena Lloyd Dube > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > 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. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
