[postgis-devel] Issue 74 in postgis: AddGeometryColumn does notdetect search_path properly
kneufeld at refractions.net
Tue Dec 2 13:32:34 PST 2008
Yeah, this is the problem of merging specifications: SQL/MM has ST_Point, SimpleFeatures has POINT. It looks like it's
all laid out in Table B1 (page69) comparing the differences between the standards.
K. I'll change the geometry constraint to use geometrytype().
Obe, Regina wrote:
> Always good to have documentation when the memory fails
> That's why GeometryType was the only non ST I kept
> When reading MM documents I do see a lot of reference to
> So I thought the behavior was intentional. See for example DB2 and they
> seem to be the most OGC compliant of all the spatial dbs out there.
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of
> codesite-noreply at google.com
> Sent: Tuesday, December 02, 2008 4:11 PM
> To: postgis-devel at postgis.refractions.net
> Subject: [postgis-devel] Issue 74 in postgis: AddGeometryColumn does
> notdetect search_path properly
> Comment #7 on issue 74 by ke... at refractions.net: AddGeometryColumn does
> detect search_path properly
> Umm. Yup, you're correct, I misread my skim read of the function ...
> concatenation at the end of the function.
> In any case, I agree that this is not correct behaviour as it does not
> follow the specs.
More information about the postgis-devel