On May 15, 11:42 am, Spk <andrew_kug...@mitel.com> wrote: > It seems that everytime I restart the web server, I get a new session > ID which is why it thinks that there is data to be commited. The > browser still has the cookie for the previous session ID, and it is > stored in the database, so why is Django generating a new session ID > each time the web server is restarted?
Yes, why indeed? Is not all information required to maintain the session persistent here? Otherwise, wouldn't you get a new session each time you hit an apache child that you'd never talked to? Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
