Hi there,
not sure if I understand your scenario correctly, but it seems to me,
that Daniel might be right about the ForeignKey being in the Location
as the wrong idea. If you need multiple locations for one Event, then
there's ManyToManyField for that (or possibly two ForeignKey(Location)
attributes of the Event model if there are always two locations..).
Anyway, defined in either way, the ORM should be able to get the data
for you without using raw sql..
Michal
On Jun 29, 12:25 pm, 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.
>
> 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)
>
> Nevertheless if there is no way to make the foreign key relationship work
> with the current schema then I will move it as you have suggested.
>
> Do you know how to build the admin.py to circumvent this issue?
>
> On Mon, Jun 29, 2009 at 6:51 PM, Daniel Roseman <dan...@roseman.org.uk>wrote:
>
>
>
> > On Jun 29, 4:57 am, Sam Walters <mr.sam...@gmail.com> wrote:
> > > Hi
> > > I am using django 1.0 to redevelop a website.
> > > I have readhttp://docs.djangoproject.com/en/1.0/topics/db/queries/andcant
> > > work out how to do my query except using raw sql. It would be great to be
> > > able to use the django query api so i can stack queries more easily.
>
> > > Just one working example would be enough for me to be able to figure out
> > the
> > > rest of the syntax i need.
> > > In this case the model is using a ForeignKey relationship between two
> > > tables, thus is a one to many relationship.
>
> > > the model.py code exists here:http://pastebin.com/m7ddf3bb8
>
> > > the views.py code exists here:http://pastebin.com/m78daa247
>
> > > I would like to be able to replace the customer sql cursor.generate
> > methods.
>
> > > Any help would be appreciated and allow me to discover a lot more about
> > > django queries.
>
> > You don't need to explicitly join the tables - that's the whole point
> > of having a foreignkey field in the model. However, there is one
> > problem. It seems like your foreign key is on the wrong model. Surely
> > each event has a single location, but a location can have many events?
> > In which case, the FK should be from event to location.
>
> > class Event (models.Model):
> > ....
> > location = models.ForeignKey(Event)
>
> > Now, you can get the events like this:
>
> > events = Event.objects.filter(start__gte=datetime.datetime.now
> > ()).select_related()
>
> > and iterate through in your template:
>
> > {% for event in events %}
> > {{ event.title }} - {{ event.location.name }}
> > {% endfor %}
>
> > The select_related() on the initial query is optional, but will get
> > all the joined location data in one query and so cut down on database
> > access.
> > --
> > 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
-~----------~----~----~----~------~----~------~--~---
