Users Discussion
*Subject:* Re: [postgis-users] operator is not unique: text || geometry
(better to stay on list )
I meant
---
RAISE EXCEPTION '%',_q ;
---
You must understand that plpgsql function fabricate on the fly SQL
statement (meaning, at execution time).
That means that without
the r.shape and cleantopo parameters?
Sorry to be so dense.
Thanks,
Steve
*From:* Rémi Cura [mailto:remi.c...@gmail.com]
*Sent:* Wednesday, February 18, 2015 1:59 PM
*To:* Miller, Stephan
*Subject:* Re: [postgis-users] operator is not unique: text || geometry
As I wrote before
Here is the cleaned version, still no good tough.
I don't understand what you want to do, I don't have your table structure
nor your data, so you will need to work from that.
CREATE OR REPLACE FUNCTION hc_check_gaps_in_linear_topology(IN tablename
text, IN cleantopo text)
RETURNS
suggestions would be appreciated.
Steve
From: Rémi Cura [mailto:remi.c...@gmail.com]
Sent: Tuesday, February 17, 2015 4:56 AM
To: PostGIS Users Discussion; Miller, Stephan
Subject: Re: [postgis-users] operator is not unique: text || geometry
Hey Stephan,
I'm afraid I must say the coding style
On Mon, Feb 16, 2015 at 10:02:14PM +, Miller, Stephan wrote:
I highlighted where I think the error is occurring in red below.
Please, *please*, don't use colors to highlight texts.
I know we're in 2015 and the internet is full of colorful moving puppets,
but if we stick to low tech it's
Hey Stephan,
I'm afraid I must say the coding style is not good and dangerous.
And I know that the very nature of plpgsql langage (and doc) make it
difficult to produce a nice function.
AS it is, it is very hard to read it, and any user of your function could
potentially inject SQL via your
All -
I am running the following PostGIS configuration on PostgreSQL 9.2
POSTGIS=2.0.6 r12554 GEOS=3.4.2-CAPI-1.8.2 r3921 PROJ=Rel. 4.8.0, 6 March
2012 GDAL=GDAL 1.9.2, released 2012/10/08 LIBXML=2.7.6 LIBJSON=UNKNOWN
TOPOLOGY RASTER
I have successfully validated topology for a single feature
