So the documentation is incorrect? It claims that it is multi-process safe.
On Jun 23, 6:53 pm, Malcolm Box <[email protected]> wrote: > Re your cacheing problem the behaviour you are seeing is exactly what would > be expected using locmem cache. > > Apache is presumably running multiple processes each of which will have it's > own locmem cache. Since the odds ate against two successive requests hitting > the same apache process, you won't see the data in your cache. > > The simplest fix is to use memcached. > > HTH > Malcolm > > Sent from my iPhone, please excuse any typos > > On 23 Jun 2011, at 22:00, John <[email protected]> wrote: > > > > > O.K. I know that there are a lot of suggestions out there for this > > problem, I think I have tried all of them but I am still getting the > > dreaded error in the subject line loading the MySQLdb module. > > > Everything was working fine, but I was having problems with a > > LocMemCache so I decided to upgrade from Django 1.2.3 to Django 1.3. > > At the same time I decided to move to Python 2.6 to Python 2.7. This > > is on Mac SnowLeopard on a MacBook Pro. > > > I have tried build and install of the MySQL-python-1.2.3 connector > > using ARCHFLAGS="-arch i386", "-arch -686", "-arch x86-64" and "-arch > > x86-32". I get the same error in all cases. I can see that the > > module being loaded is the one that was built and installed in each > > case. > > > ALso, since it was mentioned as the reason for moving to Django 1.3, > > does anyone have any suggestions for solving my cache problem? I am > > trying to save a rather large dictionary of financial calculation > > numbers to a LocMemCache. In the debug environment it works just fine > > but when I deploy to an Apache http server the cache seems to get > > cleared between each HTTP request. Via logging I can confirm that the > > object is serialized to the cache and can be immediately retrieved > > form the cache but the object no longer exists when the next HTTP > > request comes in on the same session. > > > Thank you for your asistance. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" 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 > > athttp://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
