On Aug 19, 7:08 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> My urls.py looks like this:
>
> project_info = {
> "queryset" : project.objects.all(),
>
> }
>
> (r'^project/(?P<slug>[-\w]+)/',
> login_required(list_detail.object_detail), dict(project_info,
> slug_field='slug')),
>
> Projects have a one to many relationship with tasks. The objective of
> my using object_detail is to show which tasks are applicable to the
> specificied project (slug).
>
> I am having difficulty understanding how the SQL Join can take place.
> The above appears to only get the project details from the project
> model, but not query the tasks also to see which apply. I need some
> form of filter I guess but can't find the right info I need from the
> Django docs.
>
> Any help would be much appreciated.
>
> Thanks
The SQL join is done automatically, and you would put the necessary
logic in the template.
The template is passed the project instance identified by the slug you
passed in the URL. The project model has an automatically-generated
attribute which relates an instance to its tasks - probably task_set,
which you can use like a normal queryset so you can do
x.task_set.all() to get all the tasks related to x.
So in the template, I would do something like this, given that the
list_detail generic view pass the instance as 'object':
<ul>
{% for task in object.task_set.all %}
<li>{{ task }}</li>
{% endfor %}
</ul>
--
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
