The docs say this has changed to get_queryset in dev version, 1.5 uses
get_query_set
isn't this a rather.. radical change? Is backwards compatibility
maintained somehow?
On Sun, Jun 2, 2013 at 12:40 PM, Tomas Neme wrote:
> django.db.models.manager, L118
>
> it seems to be "get_query_set" not "ge
django.db.models.manager, L118
it seems to be "get_query_set" not "get_queryset"
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@google
I omitted the code from the sample, but I do have that. The issue
seems to be that when the admin page loads, it's neither hitting the
deafault get_queryset() method in the ModelAdmin, not hitting the
proxy model's default manager methods. This is likely to be a bug.
On Tue, May 28, 2013 at 11:35
Silly, but aren't you missing
class Patient()
save(self):
self.kind = 'p'
super(Patient, self).save()
or some such thing and something similar for Doctor? I guess it might be in
the forms, but since it's nowhere in the code you showed...
--
You received this message beca
Hi everyone, I've created a custom User model and reated a proxy for
it, like this:
class User(AbstractUser):
USER_KINDS = (
('d', 'doctor'),
('p', 'patient')
)
kind = models.CharField(max_length=2, choices=USER_KINDS)
class DoctorManager(BaseUserManager):
def get
5 matches
Mail list logo
