From d69ebce53385b7c6fafb85fdab3b136dbf3f332c Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Tue, 29 May 2018 20:11:24 -0700 Subject: [PATCH] Fixed broken :ref: --- docs/spatialite.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spatialite.rst b/docs/spatialite.rst index 93efd3ff..dc9a4d14 100644 --- a/docs/spatialite.rst +++ b/docs/spatialite.rst @@ -73,7 +73,7 @@ Here's a recipe for taking a table with existing latitude and longitude columns, Making use of a spatial index ============================= -SpatiaLite spatial indexes are R*Trees. They allow you to run efficient bounding box queries using a sub-select, with a similar pattern to that used for :ref:`_full_text_search_custom_sql`. +SpatiaLite spatial indexes are R*Trees. They allow you to run efficient bounding box queries using a sub-select, with a similar pattern to that used for :ref:`full_text_search_custom_sql`. In the above example, the resulting index will be called ``idx_museums_point_geom``. This takes the form of a SQLite virtual table. You can inspect its contents using the following query::