On 7/2/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > You are always going to have to specify the weblog_id (or whatever > condition you are filtering on) somewhere and you are going to have to > put in some logic somewhere to convert a request into the right > weblog_id. The latter can be done by request context processors, so > there's no repetition there, either.
It could also be done with middleware; for example, if he's using generic views he could pass 'Entry.objects.all()' or whatever his model's QuerySet is, then have a process_view() in middleware that looks up the correct weblog and tacks a filter() onto the QuerySet before handing off to the view. Depending on exactly how he's setting things up, that might be simpler than doing a custom manager method. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
