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:14 -0500 |
| commit | 169bee85eacd5fbbf4c8f5270dbfb906934a788e (patch) | |
| tree | fbccd7fa869290e00a7d37466c72c6d3525838c9 | |
| parent | 75177681347b6e8c763f4be919908c5d3842e579 (diff) | |
[1.5.x] Fixed some punctuation; thanks Chris Jerdonek.
Backport of 81830ce34f from master
| -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 75bbca4fcf..3dfd61e921 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1397,11 +1397,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 |