[postgis-tickets] [PostGIS] #2485: [raster]: SQL functions namespace qualification (was: SQL functions namespace qualification)

[PostGIS]

#2485: [raster]: SQL functions namespace qualification
----------------------+-----------------------------------------------------
 Reporter:  rdunklau  |       Owner:  dustymugs    
     Type:  defect    |      Status:  new          
 Priority:  medium    |   Milestone:  PostGIS 2.0.5
Component:  raster    |     Version:  2.0.x        
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by robe):

  * owner:  pramsey => dustymugs
  * component:  postgis => raster
  * milestone:  => PostGIS 2.0.5


Comment:

 this will be difficult to do since people install postgis in different
 schemas and enforcing a particular schema will be hard without causing
 more damage.

 This issue you describe is only an issue for functions that call other
 functions.  The backup schema qualifies the constraint functions, so its
 the fact that this constraint function calls another function that is the
 problem.  I've had similar issue when using ST_Transform on indexes that
 my indexes don't come back unless I add a search path to the ST_Transform
 function.

 Bborie and Pierre,
 Is there any way to make this constraint function not call
 ST_BandMetaData? That is ultimately the issue. I've flagged this as a
 raster issue since I don't think we have any functions in PostGIS
 geometry/geography that are used in constraints and call other functions.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2485#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.