Opened 11 years ago
Closed 11 years ago
#2502 closed defect (fixed)
postgis_full_version() not finding topology if not in search_path
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.5 |
Component: | postgis | Version: | 2.0.x |
Keywords: | history | Cc: |
Description
If "topology" schema is not in your search_path, the "postgis_full_version()" function fails to realize that the topology is installed.
It is common for "topology" to be not in path when the extension is initially enabled.
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
This is clearly a bug and probably one you run into when you are switching from non-extension to extension install?
It's borderline. I say fix it since its clearly broken and the behavior of extension vs. non-extension is different which is a big no no already.
comment:3 by , 11 years ago
Keywords: | history added |
---|---|
Milestone: | → PostGIS 2.0.5 |
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It turns out that the "postgis_topology_scripts_installed" function is installed in the "public" schema by topology.sql but in the topology schema by CREATE EXTENSION.
I guess the correct fix for this would be to ensure the function is always created in the topology schema, and update the postgis_full_version accordingly. But... would such change be acceptable in anything but 2.2+ ?