On Wed, 2009-03-25 at 16:01 -0700, Kedare wrote: > Hello, > I'm here because i need to know if the following feature will be > included in the futures releases of django (if yes, what release ?) or > why are they missing ? > -- REAL Query cache (like in ruby on rails), very useful if you have > redundant SQL request (like multiple recursive requests by example to > show a category and it's parents)
Can also lead to inaccurate results in a lot of cases, too, so it's a two-edged sword. If you're talking about identity mapping between resources, that might come one day, however, it's so far been a mix of competing specifications by the people who've worked on it and working out a design that doesn't suck is a big part of the process. Lots of pony requests in this area, so consensus isn't easy to reach. > -- Database persistant connexion, and connexion pool, why we can keep > the connexion open in django ? we have to re-open it at every request This is out of scope for Django. There are existing applications to provide pooled connection support (e.g. pgpool for PostgreSQL) and Django should, and does, defer to them if you want that support. Replicating another applications functionality, poorly, would lead to disappointment for everybody. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
