[postgis-devel] Issue 74 in postgis: AddGeometryColumn does notdetect search_path properly
robe.dnd at cityofboston.gov
Tue Dec 2 13:18:52 PST 2008
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.
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.
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
postgis-devel mailing list
postgis-devel at postgis.refractions.net
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.
More information about the postgis-devel