On Thu, Mar 26, 2009 at 8:08 PM, Brett Parker <idu...@sommitrealweird.co.uk> wrote: > Doesn't that mean sessions would be broken, though? Public website > without write access to the database -> no session data...
Only if you are using the database to store session data. Django provides several session backends as alternatives to the database session backend. If your application is big enough that master-slave replication is required, moving sessions out of the database may be an optimization worth looking into. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
