[postgis-devel] EMPTY is as EMPTY does?

[Paul Ramsey]

Found another one, lurking in the depths of EMPTY

  select st_astext('MULTILINESTRING(EMPTY,EMPTY)'::geometry::bytea::geometry);

returns 

  MULTILINESTRING EMPTY

Basically our WKB emitter short-circuits on anything that answers true to lwgeom_is_empty() and emits a simple empty of the parent type. So it’s not possible to dump/restore a table that contains a collection empty.

In related news, gserialized_is_empty doesn’t currently handle collections of empty, it’ll return true for those, unlike lwgeom_is_empty. This is causing some inconsistent results…

ATB,

P


-- 
http://postgis.net
http://cleverelephant.ca

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150624/fd8715a3/attachment.html>