Ticket #12678: 12678.diff

File 12678.diff, 2.4 KB (added by timo, 6 years ago)

spot this ticket mentions plus others

  • docs/topics/db/models.txt

     
    10811081Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will
    10821082be ordered by ``username``.
    10831083
    1084 Querysets still return the model that was requested
     1084QuerySets still return the model that was requested
    10851085~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    10861086
    10871087There is no way to have Django return, say, a ``MyUser`` object whenever you
  • docs/topics/db/aggregation.txt

     
    9696=================================================
    9797
    9898The second way to generate summary values is to generate an independent
    99 summary for each object in a ``Queryset``. For example, if you are retrieving
     99summary for each object in a ``QuerySet``. For example, if you are retrieving
    100100a list of books, you may want to know how many authors contributed to
    101101each book. Each Book has a many-to-many relationship with the Author; we
    102102want to summarize this relationship for each book in the ``QuerySet``.
     
    257257
    258258Ordinarily, annotations are generated on a per-object basis - an annotated
    259259``QuerySet`` will return one result for each object in the original
    260 ``Queryset``. However, when a ``values()`` clause is used to constrain the
     260``QuerySet``. However, when a ``values()`` clause is used to constrain the
    261261columns that are returned in the result set, the method for evaluating
    262262annotations is slightly different. Instead of returning an annotated result
    263263for each result in the original ``QuerySet``, the original results are
  • docs/ref/models/querysets.txt

     
    9292than the results that are currently in the database.
    9393
    9494If you only want to pickle the necessary information to recreate the
    95 ``Queryset`` from the database at a later time, pickle the ``query`` attribute
     95``QuerySet`` from the database at a later time, pickle the ``query`` attribute
    9696of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without
    9797any results loaded) using some code like this::
    9898
Back to Top