On Thu, Oct 16, 2008 at 7:11 AM, Rajeev J Sebastian <[EMAIL PROTECTED]> wrote: > Without trying to read deeply between the lines, the thread seemed to > come to a point where the one choice would be to document the cases > where in the core (i.e., django+contrib) a GET request could cause a > db write. I *think* thats where Amit is now. (He also mentioned this > as the second option)
And the answer is... *any* GET request may end up causing a DB write. That's what happens when you have things like middleware and configurable view arguments available. So as Ned pointed out, it's up to someone developing an application, if they have extremely strong feelings about this, to ensure they don't configure anything which will do it. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
