On Jan 30, 4:15 pm, Tim Arnold <a_j...@bellsouth.net> wrote: > Hi, I have two basic models for a book-production site: > book configuration > build reports > > I want to display information for a particular book so you can drill- > down from a summary of its configuration and build to a detailed view > of its configuration and build report. > > The way I have it set up now is with three urls: > bookname/summary (aggregates data from both models) > bookname/configuration > bookname/build-report > > People always view the site starting with the summary. So I hit the > database once for that, and then again for each of the other views > when they drill-down. > > I read the docs on caching, but I'm no expert--is caching the smart > way to handle this? Should I worry about it? > thanks, > --Tim
Short answers: no, caching isn't the way to handle it; and no, you shouldn't worry about it. Caching is best for repeated views of the same page, or multiple pages where there are repeated complex elements. This isn't your use case - the only link between the summary and the other pages is that they refer to the same bookname. The number of repeated elements is very low, and best handled by simply getting the relevant database objects each time (this is, after all, what databases do best). Unless you're expecting a huge number of views, or have extremely low- powered database hardware, I wouldn't worry. -- DR. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
