Ticket #1287 (closed defect: fixed)
Drop of "gist_geometry_ops" broke a few clients
|Reported by:||strk||Owned by:||robe|
Brushtyler, on my left right now, had "gist_geometry_ops" use in his QGis plugin.
Indepentently, some geo-django module (on my right, with elpaso) uses "gist_geometry_ops".
Both fail against PostGIS-2.0.0SVN.
Looking at the code, we changed the name of it to "gist_geometry_ops_2d" to have space for "gist_geometry_ops_nd".
Is it worth it ?
Note that neither brushtyler, nor probably the geo-django people did anything weird, but probably just followed the PostGIS documentation (containing the instruction of using "gist_geometry_ops" when creating indices).
So, this is yet another compatibility issue to deal with.
Beside, I'm not sure what happens on incremental upgrades (if both geometry ops are left dangling in the DB, with possibly horrible consequences).