From cabf1fe37e46b00c14ed025a176628e748837658 Mon Sep 17 00:00:00 2001 From: Carlton Gibson Date: Thu, 24 Oct 2019 15:16:25 +0200 Subject: [PATCH] Refs #30897 -- Made cosmetic edits to QuerySet.explain() documentation. --- docs/ref/models/querysets.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 766a379a13..e1d188b269 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -2569,12 +2569,12 @@ The output differs significantly between databases. ``explain()`` is supported by all built-in database backends except Oracle because an implementation there isn't straightforward. -The ``format`` parameter changes the output format from the databases's default, -usually text-based. PostgreSQL supports ``'TEXT'``, ``'JSON'``, ``'YAML'``, and -``'XML'`` formats. MariaDB and MySQL support ``'TEXT'`` (also called -``'TRADITIONAL'``) and ``'JSON'`` formats. MySQL 8.0.16+ also supports an -improved ``'TREE'`` format, which is similar to PostgreSQL's ``'TEXT'`` output -and is used by default, if supported. +The ``format`` parameter changes the output format from the databases's +default, which is usually text-based. PostgreSQL supports ``'TEXT'``, +``'JSON'``, ``'YAML'``, and ``'XML'`` formats. MariaDB and MySQL support +``'TEXT'`` (also called ``'TRADITIONAL'``) and ``'JSON'`` formats. MySQL +8.0.16+ also supports an improved ``'TREE'`` format, which is similar to +PostgreSQL's ``'TEXT'`` output and is used by default, if supported. Some databases accept flags that can return more information about the query. Pass these flags as keyword arguments. For example, when using PostgreSQL::