[postgis-devel] [PostGIS] #223: Breaking change ST_Extent returns a box3d_extent object
PostGIS
trac at osgeo.org
Tue Jul 14 15:18:10 PDT 2009
#223: Breaking change ST_Extent returns a box3d_extent object
----------------------+-----------------------------------------------------
Reporter: robe | Owner: pramsey
Type: defect | Status: new
Priority: medium | Milestone: postgis 1.4.0
Component: postgis | Version:
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by robe):
On closer inspection, there are two things going on here. I think our
postgis_upgrade.sql is missing casts for box3d_extent. I had two versions
of this database. One I restored on top of a fresh 1.4 vanilla db and one
I upgraded with the upgrade script. I think its the one I upgraded that
was missing the auto cast. Though hmm I think the other one is giving a
ERROR: function get_coords(box3d_extent) is not unique
LINE 6: get_coords(ST_Extent(the_geom)) As acoord
(because I have one function for geometry and one for box2d to handle the
extent.) In that on. So I had to delete my box2d one and create nothing or
create a box3d_extent. Resulting in very sluggish performance (though
that may be unrelated) Still need to investigate why its no longer using
an index.
I guess I'll have to retrace my steps on this one to figure out if this
is just an isolated issue on my database.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/223#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS
More information about the postgis-devel
mailing list