Thanks,
I am using 1.1 beta and proxy looks like it was meant to do what I
want, without a kludge.
will give it a shoot
On Jul 19, 3:36 pm, Alex Gaynor wrote:
> On Sun, Jul 19, 2009 at 5:07 PM, Some Guy wrote:
>
> > Thanks for the help :-)
>
> > overriding queryset in modeladmin worked for the
On Sun, Jul 19, 2009 at 5:07 PM, Some Guy wrote:
>
> Thanks for the help :-)
>
> overriding queryset in modeladmin worked for the filtering.
>
> as for the subclassing of the model..
>
> I've basically got a table with lots of columns ex.[a,b,c,d,e,f,g...]
> I would like to have one admin page sho
Thanks for the help :-)
overriding queryset in modeladmin worked for the filtering.
as for the subclassing of the model..
I've basically got a table with lots of columns ex.[a,b,c,d,e,f,g...]
I would like to have one admin page show a,b,c,d and another that
shows a,b,c,f,g based (ideally) on a
I'm not entirely clear what you're trying to accomplish, but in
general when I hear "dummy" anything, I have to think there's a better
solution. Perhaps what you're looking for is an abstract model class,
from which you can subclass your two concrete ones? See
http://docs.djangoproject.com/en/dev/
hrmm, I found this too..
http://blog.dougalmatthews.com/2008/10/filter-the-django-modeladmin-set/
the method used is def queryset(self, request): in the model admin
class...
This method is not in the docs, though.
Should any of these methods be preferred over the others?
any advice is appreciate
In an attempt to answer my own question...
Would a custom manager be able to do this? I've never done one, but
could one override the all() method to filter the results that the
admin receives?
On Jul 19, 12:17 pm, Some Guy wrote:
> I was wondering if it's possible to have an admin page always
6 matches
Mail list logo
