[postgis-devel] Testing ST_LineMerge issue

[Paul Ramsey]

Our parser doesn't let that be created (does it?) so why should a
constructor?  I think as long as our policy is consistent, we're doing
OK.

P.

On Wed, Dec 17, 2008 at 7:33 AM, Obe, Regina <robe.dnd at cityofboston.gov> wrote:
> I was thinking about this failed test more and even though I had
> dismissed it as something only a Monkey would do that is not urgent.
>
> It has occurred to me that I may run into this issue with Monkey users
> and I may have already that may be a culprit in my geoserver random
> disconnects.
>
> At least one of the projects I'm working on I have run into users
> creating invalid geometries.  Since they put in a lot of effort making
> these monsters, we decided to just check on some schedule to make sure
> the new geometries being created are valid.
>
> The monster I am talking about is this innocent one that I took out of
> the torture script because well you can't torture a dead server.
>
> In its simplest form it looks like this.
>
> SELECT ST_LineMerge(ST_MakeLine(ST_Point(1,1), ST_Point(1,1)));
>
>
> Now there are 2 issues here.
>
> 1) GEOS ST_LineMerge is obviously not smart enough to realize that
> linemerging something like that is silly.
>
> 2) ST_MakeLine lets you get away with creating this monstrosity.  Which
> hmm I suppose there are reasons why someone may want to, but perhaps we
> shouldn't go there.
>
>
>
>
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>