[postgis-devel] EMPTY is as EMPTY does?

[Paul Ramsey]

Yes, it should be safe at an app level. I ran into the case though, because we had a query that was bringing down one server, but couldn’t be replicated on others… why? because when we tried to move the data to a test server it had to go through dump/restore which effectively removed the case (MULTILINESTRING(EMPTY,EMPTY)) that was causing the crash. So it’s a problem of correctness in that we cannot replicate a database exactly using dump/restore. Of course, we already have that in one case (POINT EMPTY) but maybe we don’t want to deliberately have it for other cases too.

ATB,

P 

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


On June 24, 2015 at 12:55:53 PM, Sandro Santilli (strk at keybit.net) wrote:

Which constraint would that fail ? Your example above has a MULTILINESTRING
in and a MULTILINESTRING out, sounds "safe" (although struct-breaking).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150624/ad7aae32/attachment.html>