From 993613ffdcca903da4da726ff865a22ccfd80355 Mon Sep 17 00:00:00 2001 From: Sandro Santilli Date: Mon, 12 Jun 2017 15:17:00 +0000 Subject: [PATCH] geomentry -> geometry Thanks Andreas Schild via https://www.transifex.com/postgis/postgis/translate/#de/using_postgis_datamanxmlpot/19191543/ git-svn-id: http://svn.osgeo.org/postgis/trunk@15427 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/using_postgis_dataman.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml index fc73d61c0..bebdd7e74 100644 --- a/doc/using_postgis_dataman.xml +++ b/doc/using_postgis_dataman.xml @@ -805,7 +805,7 @@ SELECT populate_geometry_columns('myschema.my_special_pois'::regclass); -- set new optional use_typmod argument to false SELECT populate_geometry_columns('myschema.my_special_pois'::regclass, false); -Although the old-constraint based method is still supported, a constraint-based geomentry column used directly +Although the old-constraint based method is still supported, a constraint-based geometry column used directly in a view, will not register correctly in geometry_columns, as will a typmod one. In this example we define a column using typmod and another using constraints. CREATE TABLE pois_ny(gid SERIAL PRIMARY KEY -- 2.50.1