From: Sandro Santilli Date: Thu, 20 Aug 2015 15:00:02 +0000 (+0000) Subject: Fix typo in PopulateGeometryColumns docs X-Git-Tag: 2.2.0rc1~137 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f41a47d9b44be9708cd1c5c2d5a3884cfac0fb9f;p=postgis Fix typo in PopulateGeometryColumns docs Thanks Oliver Tonnhofer for spotting this git-svn-id: http://svn.osgeo.org/postgis/trunk@13951 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/reference_management.xml b/doc/reference_management.xml index 8f40af486..a0299174b 100644 --- a/doc/reference_management.xml +++ b/doc/reference_management.xml @@ -837,7 +837,7 @@ GDAL="GDAL 1.11.0, released 2014/04/16" LIBXML="2.7.8" LIBJSON="0.12" RASTER Ensures geometry columns have appropriate type modifiers or spatial constraints to ensure they are registered correctly in geometry_columns table. - For backwards compatibility and for spatial needs such as tble inheritance where each child table may have different geometry type, the old check constraint behavior is still supported. + For backwards compatibility and for spatial needs such as table inheritance where each child table may have different geometry type, the old check constraint behavior is still supported. If you need the old behavior, you need to pass in the new optional argument as false use_typmod=false. When this is done geometry columns will be created with no type modifiers but will have 3 constraints defined. In particular, this means that every geometry column belonging to a table has at least