db.models.query.QuerySet.iterator()

iterator() Evaluates the QuerySet (by performing the query) and returns an iterator (see

2016-10-09 18:36:12
db.models.query.QuerySet.defer()

defer(*fields) In some complex data-modeling situations, your models might contain a lot of fields, some of which could contain

2016-10-09 18:36:07
db.models.query.QuerySet.ordered

ordered True if the QuerySet is ordered — i.e. has an order_by() clause or a default

2016-10-09 18:36:14
db.models.query.QuerySet.all()

all() Returns a copy of the current QuerySet (or QuerySet subclass). This can be useful in

2016-10-09 18:36:04
db.models.query.QuerySet.exists()

exists() Returns True if the QuerySet contains any results, and False if not. This tries

2016-10-09 18:36:10
db.models.query.QuerySet.none()

none() Calling none() will create a queryset that never returns any objects and no query will be executed when accessing the

2016-10-09 18:36:13
db.models.query.QuerySet.values_list()

values_list(*fields, flat=False) This is similar to values() except that instead of returning dictionaries, it

2016-10-09 18:36:21
db.models.query.QuerySet.get()

get(**kwargs) Returns the object matching the given lookup parameters, which should be in the format described in Field lookups

2016-10-09 18:36:11
db.models.query.QuerySet.reverse()

reverse() Use the reverse() method to reverse the order in which a queryset’s elements are returned. Calling

2016-10-09 18:36:17
db.models.query.QuerySet.only()

only(*fields) The only() method is more or less the opposite of defer(). You call it with the fields

2016-10-09 18:36:14