mirror of https://github.com/django/django.git
Fixed some punctuation; thanks Chris Jerdonek.
This commit is contained in:
parent
b8c8241945
commit
81830ce34f
|
@ -1517,11 +1517,11 @@ where ``get_or_create`` will raise an :exc:`~django.db.IntegrityError` but the
|
||||||
object won't appear in a subsequent :meth:`~django.db.models.query.QuerySet.get`
|
object won't appear in a subsequent :meth:`~django.db.models.query.QuerySet.get`
|
||||||
call.
|
call.
|
||||||
|
|
||||||
Finally, a word on using ``get_or_create()`` in Django views: please make sure
|
Finally, a word on using ``get_or_create()`` in Django views. Please make sure
|
||||||
to use it only in ``POST`` requests unless you have a good reason not to
|
to use it only in ``POST`` requests unless you have a good reason not to.
|
||||||
``GET`` requests shouldn't have any effect on data; use ``POST`` whenever a
|
``GET`` requests shouldn't have any effect on data. Instead, use ``POST``
|
||||||
request to a page has a side effect on your data. For more, see `Safe methods`_
|
whenever a request to a page has a side effect on your data. For more, see
|
||||||
in the HTTP spec.
|
`Safe methods`_ in the HTTP spec.
|
||||||
|
|
||||||
.. _Safe methods: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1
|
.. _Safe methods: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue