Don't sessions already have standard expirations in them? Besides that, this is the admin, it's not a tool for every user of your application to be in, so there will only be a few larger sessions (and larger is still only a few K at most, if you have lots and lots of models you're filtering on). And yes, it would only keep it for the length of that user's session, I don't magically expect it to be able to suddenly transfer to another user. If I wanted that functionality, I would ask for something to be added to the admin that would print out a URL that you could give to another user to get the filtering you were just using. Which sounds handy, but is a separate ticket from what we're discussing here.
On Nov 11, 2008, at 4:47 PM, David Cramer wrote: > > Well I'm not sure storing multiple search paths is too good of an > idea, as you increase the size of the session significantly, and then > have to worry about expiring those or clearing them somehow. The > session just keeps it for that users session, vs whoever else happens > to visit that url (say I pass it off to a coworker). > > On Nov 11, 3:39 pm, George Vilches <[EMAIL PROTECTED]> wrote: >> I definitely second this. The extra bonus to storing it in the >> session is that you can maintain your search state on multiple admin >> pages/models independently without overflowing the URL. Naturally if >> you do it this way, you'd also want to have a visible "clear filters" >> link so that there's some way to reset that state, I didn't check the >> patch to see if this was already included. >> >> On Nov 11, 2008, at 4:35 PM, David Cramer wrote: >> >> >> >>> Before this gets accepted, I'd like to throw in the proposal of >>> storing this in the session vs a huge URL. That and a hash seem to >>> be >>> the common approach to storing search paths. >> >>> On Nov 11, 7:19 am, Jonas Pfeil <[EMAIL PROTECTED]> wrote: >>>> Currently if you search in the admin, use some kind of filter or >>>> even >>>> just go to the second page in the change list this selection is >>>> reset >>>> when you edit an item and hit save. The user gets the default list >>>> again. Needless to say this can be quite annoying. Especially if >>>> you >>>> want to edit a specific subset of a very large database. >> >>>> The solution is to somehow make the filters persistent. The ticket >>>> [1] >>>> already has a patch. >> >>>> Cheers, >> >>>> Jonas >> >>>> [1]http://code.djangoproject.com/ticket/6903 > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
