From 11e327a3ff84e16ceace13ea6ec408a93ca9e72c Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Fri, 15 Nov 2019 16:20:07 -0500 Subject: Fixed #30988 -- Deprecated the InvalidQuery exception. It was barely documented without pointers at its defining location and was abused to prevent misuse of the QuerySet field deferring feature. --- docs/topics/db/sql.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/topics') diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt index f0af7a4b44..355c7366ca 100644 --- a/docs/topics/db/sql.txt +++ b/docs/topics/db/sql.txt @@ -170,8 +170,9 @@ last names were both retrieved on demand when they were printed. There is only one field that you can't leave out - the primary key field. Django uses the primary key to identify model instances, so it -must always be included in a raw query. An ``InvalidQuery`` exception -will be raised if you forget to include the primary key. +must always be included in a raw query. A +:class:`~django.core.exceptions.FieldDoesNotExist` exception will be raised if +you forget to include the primary key. Adding annotations ------------------ -- cgit v1.3