diff options
| author | Tim Graham <timograham@gmail.com> | 2014-01-23 09:01:26 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-01-23 09:05:09 -0500 |
| commit | c91e772b3a5bf45b690645001386339e7a268bd7 (patch) | |
| tree | c104b39d18231e6dd268fff11f21952d65d52636 /docs/ref/models | |
| parent | 6bf05c0267b388bdf6f2bda6f1915c1ac8a02b35 (diff) | |
[1.6.x] Fixed some punctuation; thanks Chris Jerdonek.
Backport of 81830ce34f from master
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/querysets.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index dc51e26366..69e15dc0e9 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1458,11 +1458,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` call. -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 -``GET`` requests shouldn't have any effect on data; use ``POST`` whenever a -request to a page has a side effect on your data. For more, see `Safe methods`_ -in the HTTP spec. +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. +``GET`` requests shouldn't have any effect on data. Instead, use ``POST`` +whenever a request to a page has a side effect on your data. For more, see +`Safe methods`_ in the HTTP spec. .. _Safe methods: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1 |