[3.0.x] Used 🎫 role in all tickets links.

Backport of abc51d44af from master
This commit is contained in:
Sergey Fedoseev 2019-11-25 20:28:47 +05:00 committed by Mariusz Felisiak
parent 3ed55606c4
commit 314ad45c09
8 changed files with 15 additions and 24 deletions

View file

@ -199,9 +199,8 @@ modified using any other ``QuerySet`` operation, including ``filter()``,
Combining multiple aggregations
-------------------------------
Combining multiple aggregations with ``annotate()`` will `yield the wrong
results <https://code.djangoproject.com/ticket/10060>`_ because joins are used
instead of subqueries:
Combining multiple aggregations with ``annotate()`` will :ticket:`yield the
wrong results <10060>` because joins are used instead of subqueries:
>>> book = Book.objects.first()
>>> book.authors.count()

View file

@ -961,9 +961,8 @@ extra forms displayed.
Also, ``extra=0`` doesn't prevent creation of new model instances as you can
:ref:`add additional forms with JavaScript <understanding-the-managementform>`
or send additional POST data. Formsets `don't yet provide functionality
<https://code.djangoproject.com/ticket/26142>`_ for an "edit only" view that
prevents creation of new instances.
or send additional POST data. Formsets :ticket:`don't yet provide functionality
<26142>` for an "edit only" view that prevents creation of new instances.
If the value of ``max_num`` is greater than the number of existing related
objects, up to ``extra`` additional blank forms will be added to the formset,

View file

@ -275,9 +275,7 @@ setting.
Caches are not cleared after each test, and running "manage.py test fooapp" can
insert data from the tests into the cache of a live system if you run your
tests in production because, unlike databases, a separate "test cache" is not
used. This behavior `may change`_ in the future.
.. _may change: https://code.djangoproject.com/ticket/11505
used. This behavior :ticket:`may change <11505>` in the future.
Understanding the test output
-----------------------------