Hi Ned, On Thu, Oct 16, 2008 at 5:22 PM, Ned Batchelder <[EMAIL PROTECTED]> wrote: > At one point, Amit used the phrase "should Django enforce it?", which sounds > like more than documentation to me. Changing Django so that GETs couldn't > modify the database would be a bad idea. There are just too many cases > where this is a permissible operation. You are right that only small > changes should be made on GET requests, but how can Django enforce this? At > some point, the developer needs to understand the implications of their > design. This is a tradeoff of power and safety. Django needs to give > people enough rope to hang themselves, unfortunately.
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) Hope I'm right ... Regards Rajeev J Sebastian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
