From 3b18d9f3a1bcdd93280f79654eba0efa209377bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Anssi=20K=C3=A4=C3=A4ri=C3=A4inen?= Date: Sun, 12 Jan 2014 19:51:53 +0200 Subject: [PATCH] Removed suggestion of temporary lookup registration from docs --- docs/ref/models/custom_lookups.txt | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/ref/models/custom_lookups.txt b/docs/ref/models/custom_lookups.txt index ef8ec7f40e..c11bffebe2 100644 --- a/docs/ref/models/custom_lookups.txt +++ b/docs/ref/models/custom_lookups.txt @@ -216,12 +216,6 @@ When compiling a query, Django first looks for ``as_%s % connection.vendor`` methods, and then falls back to ``as_sql``. The vendor names for the in-built backends are ``sqlite``, ``postgresql``, ``oracle`` and ``mysql``. -.. note:: - If for some reason you need to change the lookup just for a specific query, - you can do that and reregister the original lookup afterwards. However you - need to be careful to ensure that your patch is in place until the queryset - is evaluated, not just created. - .. _query-expression: The Query Expression API