On Apr 11, 9:25 pm, codecowboy <guy.ja...@gmail.com> wrote: > I've read some other posts regarding this issue as well as the > following article:http://www.b-list.org/weblog/2007/nov/03/working-models/. > I cannot seem to get this thing to work. Thank you in advance for any > help. Here is my code. > > ---------- view ---------- > from django.db.models import get_model > > def blah(): > c = get_model('conferences', 'conference') > uc = c.upcoming() > > ---------- model ---------- > class Conference(models.Model): > . > . > . > > def upcoming(self): > today = datetime.today() > return self.objects.filter(date__gte=(today)) > > I've also tried the following in my view code: > > def blah(): > c = Conference() > uc = c.upcoming() > > I cannot stop the following error from displaying: > > TypeError at /scientists/portal > > unbound method upcoming() must be called with Conference instance as > first argument (got nothing instead) > > Request Method: GET > Request URL: http://127.0.0.1:8000/scientists/portal > Exception Type: TypeError > Exception Value: > > unbound method upcoming() must be called with Conference instance as > first argument (got nothing instead) > > Exception Location: /home/guy/DjangoApps/scinet/scientists/views.py > in portal, line 20
You are confused between class and instance methods. upcoming as you have defined it is an instance method - ie you call it on an instance of Conference. However, the content of the method looks like it should be a class method - that is, you call it on the Conference class itself - and, indeed, that is what you are trying to do in your blah view. There are two solutions to this: the first is to tell Python that this is a class method by simply using the @classmethod decorator - and, by convention, using cls as the parameter to the method rather than self. However, looking at what you're actually trying to do - return a custom queryset of Conference objects - the idiomatic way of achieving this in Django is actually to define a custom manager. Again, two ways of doing this: you can define an additional manager and put your method in it as get_query_set - so you would call it as Conference.upcoming.all(); or override the default manager and put your method as upcoming - so you would call it as Conference.objects.upcoming(). Your choice. See here for information on custom managers: http://docs.djangoproject.com/en/dev/topics/db/managers/ -- 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 -~----------~----~----~----~------~----~------~--~---
