[postgis-devel] Call for 1.4.2 and 1.5.1 (Handling of Invalid Geometries)

[Kevin Neufeld]

What if the shp loader were modified so that it didn't use addgeometrycolumn but rather apply the constraints *after* 
the table was created and loaded.

The loader could keep track of the geometry types it inserts and add an appropriate common denominator geometrytype 
constraint.

(I was going to suggest the loader could use populate_geometry_columns, but I just discovered a bug in the script when 
trying to apply constraints to such a table.)

-- Kevin

On 2/24/2010 9:18 AM, strk wrote:
> Mmm, I'm not convinced about this.
> The ST_MakeValid function easily returns GEOMETRYCOLLECTION in its attempt
> to keep all points. This mean the geometries will not be accepted in a table
> crated with ST_AddGeometryColumn because that call will enforce a constraint
> on geometry type.
>