On 6/6/06, Bill de hÓra <[EMAIL PROTECTED]> wrote: > I understand why you might need this, but at the HTTP level, when the > example for this goes into the docs, can it be wrapped inside a > request.POST? That will stop someone somewhere from using get_or_create > via a GET view.
Sure, Bill -- good call. I think get_or_create() is more useful out of Web-request contexts (namely, in scripts that import data and do a lot of object creation), but I'll explicitly point the POST preference in the docs. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
