Fixed #2356 -- Removed references to get_object() from docs/tutorial03.txt. Thanks, toddobryan
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3356 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
4537cf3dd4
commit
6870edf2a0
|
@ -288,7 +288,7 @@ exception if a poll with the requested ID doesn't exist.
|
|||
A shortcut: get_object_or_404()
|
||||
-------------------------------
|
||||
|
||||
It's a very common idiom to use ``get_object()`` and raise ``Http404`` if the
|
||||
It's a very common idiom to use ``get()`` and raise ``Http404`` if the
|
||||
object doesn't exist. Django provides a shortcut. Here's the ``detail()`` view,
|
||||
rewritten::
|
||||
|
||||
|
@ -313,8 +313,8 @@ exist.
|
|||
foremost design goals of Django is to maintain loose coupling.
|
||||
|
||||
There's also a ``get_list_or_404()`` function, which works just as
|
||||
``get_object_or_404()`` -- except using ``get_list()`` instead of
|
||||
``get_object()``. It raises ``Http404`` if the list is empty.
|
||||
``get_object_or_404()`` -- except using ``filter()`` instead of
|
||||
``get()``. It raises ``Http404`` if the list is empty.
|
||||
|
||||
Write a 404 (page not found) view
|
||||
=================================
|
||||
|
|
Loading…
Reference in New Issue