Ticket #464 (closed defect: wontfix)

Opened 3 years ago

Last modified 12 months ago

ST_Dump ignores empties

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

Description

strk=# select path,st_astext(geom) from st_dump('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(POINT(0 0),POINT(1 1)),LINESTRING(10 0, 20

0),GEOMETRYCOLLECTION(GEOMETRYCOLLECTION EMPTY))'); path | st_astext


{1,1} | POINT(0 0) {1,2} | POINT(1 1) {2} | LINESTRING(10 0,20 0)

(3 rows)

It's missing {3.1} ...

... may the semantic debate begin ;)

Change History

Changed 2 years ago by robe

  • milestone changed from PostGIS 1.5.3 to PostGIS 1.5.4

Changed 13 months ago by pramsey

I think this is pointless. The use case of dump is getting ones hands on useful objects to analyze. Empties add nothing to the soup.

Changed 12 months ago by robe

  • status changed from new to closed
  • resolution set to wontfix

I agree its pointless too +1.

Note: See TracTickets for help on using tickets.