On Jun 29, 11:25 am, Sam Walters <mr.sam...@gmail.com> wrote:
> Hi Daniel
> Thank you very much for your help.
> The reasons why the foreign key is in the other table is because an event
> can have multiple locations, its unusual however the Aviation industry has
> an event which will fly from location A to B. Yes it seems counter-intuitive
> at first glance.
Fair enough. The same principles apply though - you just get the
events, then iterate through in the template and refer to the
locations via the event objects. The difference is that it's now a
'backwards relation' - see the query documentation for more on this -
so you get the related items via event.location_set.all() (missing out
the brackets in the template) and since it's a queryset you will need
to iterate through this in turn.
{% for event in events %}
{{ event.title }}
{% for location in event.location_set.all %}
{{ location.name }}
{% endfor %}
{% endfor %}
Note that this way select_related doesn't work, so if you have lots of
events/locations the number of queries required might become an issue.
> The other reason is If do move the foreign key to the Events table then i
> cant get the admin.py to work. The admin has to be able to edit all the
> fields (in effect see columns from multiple tables using inlines) from the
> same page:
>
> in admin.py:
>
> class LocationInline(admin.StackedInline):
> model=Location
> extra = 0
>
> class EventAdmin(admin.ModelAdmin):
> inlines = [PeriodInline, LocationInline, InviteGroupInline,
> CategoryInline,]
> list_display = ('added','title','email',)
> list_per_page = 50
> list_filter = ('added','start','end',)
> search_fields = ('contact', 'email', 'phoneBH', 'phoneAH', 'phoneFax',
> 'phoneM', 'url','title','description')
>
> admin.site.register(Event, EventAdmin)
Well, you can't edit 'forwards' relationships via inlines - among
other things, the related object now doesn't solely belong to the one
you're viewing, so editing it inline wouldn't make sense. All you can
do in this direction is choose which object you're related to, and
potentially (via some custom templating) link to the edit screen for
that object in a popup.
--
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
