I did not have settings like this but re-organizing my project, installing django again, deleting and creating the database made the issue disappear. This implies that it must be my fault.
Thanks for all the help and time you guys spent on my problem. I am very sure that I am going to enjoy the test driven approach of django. Excellent work. Regards Kapil On Jun 13, 9:53 am, "Norman Harman" <[EMAIL PROTECTED]> wrote: > ksachdevawrote: > > Hi, > > > From a testcase I first issue a 'get' request to a view (say view1) > > where I set a request.session['m_key'] = 'myval'. Now I issue a 'post' > > request to a view (say view2). In view2, I tried to obtain > > request.session['m_key'] but I get an error that session does not have > > 'm_key' key. > > I've spent a lot of time debugging session problems only to discover I > had made the bone headed mistake of having this settings combo > > CACHE_BACKEND="dummy://" > SESSION_ENGINE="django.contrib.sessions.backends.cache" > > ... > -- > Norman J. Harman Jr. > Senior Web Specialist, Austin American-Statesman > ___________________________________________________________________________ > You've got fun! Check out Austin360.com for all the entertainment > info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
