[postgis-devel] [PostGIS] #1212: [raster]: st_intersects signature change - documentation out of synch

[PostGIS]

#1212: [raster]: st_intersects signature change - documentation out of synch
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  pracine      
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 Replying to [comment:8 robe]:
 > How about this
 >
 > Make
 >
 > rast1,rast2,nband1,nband2
 >
 > just
 >
 > rast1,rast2
 >
 > Don't allow people to use bands with that version.

 This would be inconsistent with ST_Intersection(raster1, band1, raster2,
 band2) which is planned to work on single bands. (If not, what would be
 the result of ST_Intersection(raster1, raster2) if they both have multiple
 bands? This is the big question of the day!)

 > It doesn't really solve my management burden, though.  I'm more
 concerned about the permutations and the possibility of text cast to
 integer and integer to text and that kind of stuff which ends up making
 functions go the wrong path than what the user intended.

 It seems to me that those casting problems should not force us to adopt
 one signature over another one. Are we slave here or masters?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1212#comment:9>
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.