Topic guide Performing raw SQL queries

Fields may also be left out: The Person objects returned by this query will be deferred model instances (see defer()). This means that the fields that are omitted from the query will be loaded on demand.

Topic guide Creating forms from models

As you might expect, the ForeignKey and ManyToManyField model field types are special cases: ForeignKey is represented by django.forms.ModelChoiceField, which is a ChoiceField whose choices are a model QuerySet.

Topic guide Django shortcut functions

get_object_or_404(klass,*args,**kwargs)[source] aget_object_or_404(klass,*args,**kwargs) : Asynchronous version: aget_object_or_404()

Topic guide Django shortcut functions

klass A Model class, a Manager, or a QuerySet instance from which to get the object. *args Q() objects. **kwargs Lookup parameters, which should be in the format accepted by get() and filter().

Topic guide Django shortcut functions

get_list_or_404(klass,*args,**kwargs)[source] aget_list_or_404(klass,*args,**kwargs) : Asynchronous version: aget_list_or_404()

Topic guide Django shortcut functions

klass A Model, Manager or QuerySet instance from which to get the list. *args Q() objects. **kwargs Lookup parameters, which should be in the format accepted by get() and filter().

Topic guide Pagination

Under the hood, all methods of pagination use the Paginator class. It does all the heavy lifting of actually splitting a QuerySet into Page objects.

Topic guide Pagination

Here’s an example using Paginator in a view function to paginate a queryset: In the template list.html, you can include navigation between pages in the same way as in the template for the ListView above.

Topic guide Performance and optimization

Django is itself quite lazy. A good example of this can be found in the evaluation of a QuerySet. QuerySets are lazy.

Topic guide Security in Django

This can result in records being deleted or data leakage. Django’s querysets are protected from SQL injection since their queries are constructed using query parameterization. A query’s SQL code is defined separately from the query’s parameters.

Topic guide Serializing Django objects

At the highest level, you can serialize data like this: The arguments to the serialize function are the format to serialize the data to (see Serialization formats) and a QuerySet to serialize.

Index

| | | | --- | --- | | - y (LineString attribute) - (Point attribute) - year - field lookup type - year (YearMixin attribute) - year_format (YearMixin attribute) - YEAR_MONTH_FORMAT - setting | - YearArchiveView (built-in class) - …

Internals Django Deprecation Timeline

django.core.paginator.QuerySetPaginator will be removed. A model’s Meta.ordering will no longer affect GROUP BY queries. django.contrib.postgres.fields.FloatRangeField and django.contrib.postgres.forms.FloatRangeField will be removed. The FILE_CHARSET setting will be removed. django.contrib.staticfiles.storage.CachedStaticFilesStorage will be removed. RemoteUserBackend.configure_user() will require request as the first positional argument.

Reference PostgreSQL specific aggregation functions

classBitAnd(expression,filter=None,default=None,**extra) : Returns an int of the bitwise AND of all non-null input values, or default if all values are null.

Reference PostgreSQL specific aggregation functions

classBitOr(expression,filter=None,default=None,**extra) : Returns an int of the bitwise OR of all non-null input values, or default if all values are null.

Reference PostgreSQL specific aggregation functions

classBitXor(expression,filter=None,default=None,**extra) : Returns an int of the bitwise XOR of all non-null input values, or default if all values are null.

Reference PostgreSQL specific aggregation functions

classStringAgg(expression,delimiter,distinct=False,filter=None,default=None,order_by=()) : > WARNING: > > Deprecated since version 6.0: The PostgreSQL StringAgg class is deprecated in favor of the > generally available StringAgg class.

Reference Databases

These are triggered when using the iexact or contains filters in querysets. The behavior splits into two cases: For substring matching, all matches are done case-insensitively. That is a filter such as filter(name__contains="aa") will match a name of "Aabb".

Reference Conditional Expressions

What if we want to find out how many clients there are for each account_type?

Reference Model index reference

Index.condition If the table is very large and your queries mostly target a subset of rows, it may be useful to restrict an index to that subset. Specify a condition as a Q.