[postgis-tickets] [PostGIS] #2217: [raster] ST_AsBinary semantic discrepancy

[PostGIS]

#2217: [raster] ST_AsBinary semantic discrepancy
---------------------+------------------------------------------------------
 Reporter:  mloskot  |       Owner:  dustymugs
     Type:  defect   |      Status:  new      
 Priority:  medium   |   Milestone:           
Component:  raster   |     Version:  trunk    
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by pracine):

 So if I understand Mat well, having ST_AsBinary return filesystem path is
 useless and undesirable? What about an application that would reside on
 the same server as the DB and would like to read the raster directly
 (because they are already in JPEG for exmaple). And let's suppose there
 are also some raster in-db. How can this application know how to read the
 right file? It has to query for ST_BandPath() for each tables? Or it call
 for ST_AsBinary() with the switch set to return the path so it does not
 have to do an extra query (ST_BandPath()) to know if it is in-db or out-
 db. If someone never wants to read out-db directly, he just call
 ST_AsBinary() with the switch set to always return in-db like data.

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