Master / Slave Database Replication Scenario

Hi, we are using master / slave database replication, no partitioning, just replicating the complete database to several slaves for performance reasons. This is making some problems with a newly developed Django project, which makes use of an existing database. Is there an (easy) way to use a di

Re: context objects get cached/stored across requests, somehow

On Jul 6, 5:53 pm, Brian Neal wrote: > > I believe you have been hit with one of the famous Python gotchas. > > http://www.ferg.org/projects/python_gotchas.html#contents_item_6 Your're absolutely right. Thanks alot for the tip! Cheers. --~--~-~--~~~---~--~~ You

context objects get cached/stored across requests, somehow

Hi, I've created a view which displays a simple list of all objects of one model. If a 'search_string' URL parameter is defined, the list is filtered by this search string and the search string itself will be displayed in the template as well. Please have a look at the complete view here: http://