Fungsi jalan pintas Django¶
The package django.shortcuts collects helper functions and classes that
"span" multiple levels of MVC. In other words, these functions/classes
introduce controlled coupling for convenience's sake.
render()¶
-
render(request, template_name, context=None, content_type=None, status=None, using=None)[sumber]¶ Combines a given template with a given context dictionary and returns an
HttpResponseobject with that rendered text.Django does not provide a shortcut function which returns a
TemplateResponsebecause the constructor ofTemplateResponseoffers the same level of convenience asrender().
Argumen dibutuhkan¶
request- The request object used to generate this response.
template_name- The full name of a template to use or sequence of template names. If a sequence is given, the first template that exists will be used. See the template loading documentation for more information on how templates are found.
Argumen pilihan¶
context- Nilai kamus untuk ditambah ke konteks cetakan. Secara awalan, ini adalah kamus kosong. Jika nilai di kamus adalah callable, tampilan akan memanggilnya sesaat sebelum membangun cetakan.
content_type- The MIME type to use for the resulting document. Defaults to the value of
the
DEFAULT_CONTENT_TYPEsetting. status- The status code for the response. Defaults to
200. using- The
NAMEof a template engine to use for loading the template.
Contoh¶
The following example renders the template myapp/index.html with the
MIME type application/xhtml+xml:
from django.shortcuts import render
def my_view(request):
# View code here...
return render(request, 'myapp/index.html', {
'foo': 'bar',
}, content_type='application/xhtml+xml')
Contoh ini setara pada:
from django.http import HttpResponse
from django.template import loader
def my_view(request):
# View code here...
t = loader.get_template('myapp/index.html')
c = {'foo': 'bar'}
return HttpResponse(t.render(c, request), content_type='application/xhtml+xml')
render_to_response()¶
-
render_to_response(template_name, context=None, content_type=None, status=None, using=None)[sumber]¶ This function preceded the introduction of
render()and works similarly except that it doesn't make therequestavailable in the response. It's not recommended and is likely to be deprecated in the future.
redirect()¶
-
redirect(to, permanent=False, *args, **kwargs)[sumber]¶ Returns an
HttpResponseRedirectto the appropriate URL for the arguments passed.Argumen dapat menjadi:
- A model: the model's
get_absolute_url()function will be called. - A view name, possibly with arguments:
reverse()will be used to reverse-resolve the name. - An absolute or relative URL, which will be used as-is for the redirect location.
By default issues a temporary redirect; pass
permanent=Trueto issue a permanent redirect.- A model: the model's
Contoh¶
You can use the redirect() function in a number of ways.
By passing some object; that object's
get_absolute_url()method will be called to figure out the redirect URL:from django.shortcuts import redirect def my_view(request): ... object = MyModel.objects.get(...) return redirect(object)
By passing the name of a view and optionally some positional or keyword arguments; the URL will be reverse resolved using the
reverse()method:def my_view(request): ... return redirect('some-view-name', foo='bar')
By passing a hardcoded URL to redirect to:
def my_view(request): ... return redirect('/some/url/')
Ini juga bekerja dengan URL penuh:
def my_view(request): ... return redirect('https://example.com/')
By default, redirect() returns a temporary redirect. All of the above
forms accept a permanent argument; if set to True a permanent redirect
will be returned:
def my_view(request):
...
object = MyModel.objects.get(...)
return redirect(object, permanent=True)
get_object_or_404()¶
-
get_object_or_404(klass, *args, **kwargs)[sumber]¶ Calls
get()on a given model manager, but it raisesHttp404instead of the model'sDoesNotExistexception.
Argumen dibutuhkan¶
Contoh¶
The following example gets the object with the primary key of 1 from
MyModel:
from django.shortcuts import get_object_or_404
def my_view(request):
my_object = get_object_or_404(MyModel, pk=1)
Contoh ini setara pada:
from django.http import Http404
def my_view(request):
try:
my_object = MyModel.objects.get(pk=1)
except MyModel.DoesNotExist:
raise Http404("No MyModel matches the given query.")
The most common use case is to pass a Model, as
shown above. However, you can also pass a
QuerySet instance:
queryset = Book.objects.filter(title__startswith='M')
get_object_or_404(queryset, pk=1)
The above example is a bit contrived since it's equivalent to doing:
get_object_or_404(Book, title__startswith='M', pk=1)
but it can be useful if you are passed the queryset variable from somewhere
else.
Finally, you can also use a Manager. This is useful
for example if you have a
custom manager:
get_object_or_404(Book.dahl_objects, title='Matilda')
Anda dapat juga menggunakan related managers:
author = Author.objects.get(name='Roald Dahl')
get_object_or_404(author.book_set, title='Matilda')
Note: As with get(), a
MultipleObjectsReturned exception
will be raised if more than one object is found.
get_list_or_404()¶
-
get_list_or_404(klass, *args, **kwargs)[sumber]¶ Returns the result of
filter()on a given model manager cast to a list, raisingHttp404if the resulting list is empty.
Argumen dibutuhkan¶
Contoh¶
The following example gets all published objects from MyModel:
from django.shortcuts import get_list_or_404
def my_view(request):
my_objects = get_list_or_404(MyModel, published=True)
Contoh ini setara pada:
from django.http import Http404
def my_view(request):
my_objects = list(MyModel.objects.filter(published=True))
if not my_objects:
raise Http404("No MyModel matches the given query.")