From 64ed8cdc9f2f7333b2a9fd6b318f520278c39293 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C5=82awomir=20Ehlert?= Date: Wed, 6 May 2015 15:51:01 +0200 Subject: [PATCH] Fixed typos in docs/ref/contrib/gis/geoquerysets.txt --- docs/ref/contrib/gis/geoquerysets.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt index e2650cbab0..ae801c8581 100644 --- a/docs/ref/contrib/gis/geoquerysets.txt +++ b/docs/ref/contrib/gis/geoquerysets.txt @@ -279,7 +279,7 @@ Example:: # A tuple lookup parameter is used to specify the geometry and # the intersection pattern (the pattern here is for 'contains'). - Zipcode.objects.filter(poly__relate(geom, 'T*T***FF*')) + Zipcode.objects.filter(poly__relate=(geom, 'T*T***FF*')) PostGIS SQL equivalent:: @@ -301,7 +301,7 @@ strings are case-insensitive. Example:: - Zipcode.objects.filter(poly__relate(geom, 'anyinteract')) + Zipcode.objects.filter(poly__relate=(geom, 'anyinteract')) Oracle SQL equivalent::