I want persistent change filter settings in the Django admin app. This
has been discussed for years, and from some bug/feature tickets, it is
inferred to be either implemented in SVN or getting close to it. I
cannot find any documentation on it, although I'm still looking.
Anyone have any knowledge
When a model contains (along with other fields):
owner = models.ForeignKey(User, related_name="owner", blank=True,
editable=False)
class Admin:
list_filter = ('owner',)
pass
Then the admin interface has a filter for records by owner with this
url:
http://localhost:8000/admin/
Hi Picio, Luke and anyone else interested in challenging Django
problems like this,
For those new to this thread, Picio and I independently tried using
this recipe:
http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
to create model managers that only permit a logged in user to see and
I have exactly the same question, Picio. If I find an answer before
this group does, I'll let you know. Please do the same. Thanks.
Tom Miller
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
Thanks Malcom, very enlightening.
I would be very interested in learning how/where to go about
reconstructing the queryset.
Tom
Here is the relevant section of my model:
class TaskManager(models.Manager):
def get_query_set(self):
Here's a clue. I tried hosting this project from my apache2 server
using mod_python. The queryset stays in sync after updates, it works
just as expected. Perhaps it is a limitation of the built in Django
server, which after all, is not meant for production. Still, if there
is a way to get the expe
I'm using generic view create_update.update_object to edit items
selected from a generic list_detail.object_list. Edits to items work
very well, they hit the database as soon as I submit the form in my
html template. I know because I inspect the mysql table directly. So
far so good.
One of my fie
I'm using generic view create_update.update_object to edit items
selected from a generic list_detail.object_list. Edits to items work
very well, they hit the database as soon as I submit the form in my
html template. I know because I inspect the mysql table directly. So
far so good.
One of my fie
Yep, that did it. Thanks.
Actually, my urls.py was OK, it was decoupled into the application
directory. But that darn template got imported into the project sort of
late at night, and foxed me into misinterpreting the symptoms.
I have seen some template errors caught by django. Some but not all,
Russell, thanks for looking into this! See comments & code below.
Tom
Russell Keith-Magee wrote:
>
> - Are you sure that the database has been synced to match the 'with
> foreign key' version of the model? Drop the db and recreate to be
> sure.
Yes, I had done that.
> - What does the developmen
Sure, Russ, I'll be more explicit, hopefully less Zen-like.
The cheetsheet model as-is works just as expected with
django.views.generic.create_update.create_object, i.e.
1. url kicks off generic view add to template with empty fields as
expected
2. I enter data, click save
3. I get whisked back t
That is, create/update/delete generic views do not create, update, or
delete on a model (table) with a foreign key within the app or project.
At least I cannot figure out how.
They do, however, work fine on a model with a foreign key to
django.contrib.auth.models.User. I got this from the
http://
12 matches
Mail list logo
