Opened 12 years ago

Closed 10 years ago

#449 closed defect (wontfix)

Populate_Geometry_Columns should declare type to be 'GEOMETRY' when failing to apply geotype constraint

Reported by: kneufeld Owned by: kneufeld
Priority: medium Milestone: PostGIS 1.5.4
Component: postgis Version: 1.5.X
Keywords: Cc:

Description

A table with mixed geometry types obviously can't have an enforce_geotype constraint applied to the table, but geometry_columns should still have a valid record indicating the geometry type. In this case, perhaps 'GEOMETRY' or 'MIXED'.

At the moment, this function declares the type in geometry_columns to be the first geometrytype detected in the table, which is not correct.

create table foo(geom geometry);
insert into foo values ('POINT(0 0)'::geometry);
insert into foo values ('LINESTRING(0 0, 1 1)'::geometry);
select populate_geometry_columns();
select * from geometry_columns ;

 f_table_catalog | f_table_schema | f_table_name | f_geometry_column | coord_dimension | srid | type  
-----------------+----------------+--------------+-------------------+-----------------+------+-------
                 | public         | foo          | geom              |               2 |   -1 | POINT
(1 row)

Change History (4)

comment:1 by pramsey, 12 years ago

Owner: changed from pramsey to kneufeld

comment:2 by pramsey, 12 years ago

Milestone: PostGIS 1.5.1PostGIS 1.5.2

comment:3 by robe, 11 years ago

Milestone: PostGIS 1.5.3PostGIS 1.5.4

comment:4 by pramsey, 10 years ago

Resolution: wontfix
Status: newclosed

No love, no fix.

Note: See TracTickets for help on using tickets.