[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):

 We maybe don't have to document all the overloads and just says, in
 general for the specific case of band number: "Band numbers can be
 omitted. In this case they default to 1." This solve your management
 burden and keeps a certain rule about parameter's order.

 Still I think we need a written set of rules for parameters order and
 defaults. This could be added at the beginning of the reference section.

 I still prefer (rast1, int1, rast2, int2) over (rast1, rast2, int1, int2).

 PostGIS never had this problem of two many overloads because the internal
 structure of the object is more simple than raster. In our case many
 functions must get many parameters...

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