From 336c409057a36b1429cef0406c81c72207e18ee5 Mon Sep 17 00:00:00 2001 From: Josiah White Date: Sat, 22 Oct 2022 20:11:42 -0700 Subject: [PATCH] Fixed #27587 -- Removing redundant str call --- docs/intro/tutorial02.txt | 2 +- docs/topics/db/queries.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/intro/tutorial02.txt b/docs/intro/tutorial02.txt index 99812673d4..e7d727403e 100644 --- a/docs/intro/tutorial02.txt +++ b/docs/intro/tutorial02.txt @@ -478,7 +478,7 @@ Save these changes and start a new Python interactive shell by running ]> # Print the SQL used to query the database >>> from pprint import pprint - >>> pprint(str(q.query)) + >>> pprint(q.query) ('SELECT "polls_question"."id", "polls_question"."question_text", ' '"polls_question"."pub_date" FROM "polls_question"') diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index cb9a071982..1f34060252 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -344,7 +344,7 @@ When debugging a query, it may be useful to see the SQL generated by a queryset. You may do this by converting the ``query`` attribute to a string. >>> q = Entry.objects.all() - >>> str(q.query) + >>> print(q.query) This prints the SQL that is used to query the database. From there, you may look for unexpected clauses, etc. Note that this SQL may require modification