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

 Replying to [comment:15 mloskot]:
 > @pracine Database communication is based on client-server model. The
 fact that you can put application and database on the same machine is
 irrelevant here, because we discuss public SQL API which is supposed to
 provide seamless means of access.

 It is true that out-db and in-db are becoming more and more seamless but
 you still can't edit out-db. In the beginning there was no plan to be able
 to access out-db pixel values. out-db has been put there just to satisfy
 web based application developers scared that putting the data in the db
 would result in poorer reading performance.

 > I'd also argue, that in distributed systems, in a cloud, returning local
 path is useless indeed. It is not responsibility of application to read
 the file registered in PostGIS database as out-db raster, but it is
 responsibility of PostGIS to serve that file. The application does not
 want to distinguish storage modes in the server.

 So even ST_BandPath() would be irrelevant in that case?

 So why storing raster outside the database then?

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