From 76a87e711b88bfcec860a0323fa7a42beefebd3a Mon Sep 17 00:00:00 2001 From: Paul Ramsey Date: Thu, 30 Aug 2001 22:24:17 +0000 Subject: [PATCH] Typo in SQL example fixed. git-svn-id: http://svn.osgeo.org/postgis/trunk@59 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/postgis.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/postgis.xml b/doc/postgis.xml index 76cf49aa4..1a1628dd2 100644 --- a/doc/postgis.xml +++ b/doc/postgis.xml @@ -341,7 +341,7 @@ db=# "ROADS_GEOM" table in which the geometry was equal to that value. When using the "&&" operator, you can specify either a BOX3D as the comparison feature or a GEOMETRY. When you specify a GEOMETRY, - however, the bounding box will be used for the comparison.SELECT * FROM ROADS_GEOM WHERE GEOM && 'POLYGON(191232 243117,191232 243119,191234 243117,191232 243117)'::geometry; + however, the bounding box will be used for the comparison.SELECT * FROM ROADS_GEOM WHERE GEOM && 'POLYGON((191232 243117,191232 243119,191234 243117,191232 243117))'::geometry; The above query will use the bounding box of the polygon for comparison purposes. The most common spatial query will probably be a "frame-based" -- 2.50.1