[postgis-devel] [PostGIS] #152: [wktraster] raster_columns out-db field should be an array

PostGIS trac at osgeo.org
Fri Dec 18 10:52:34 PST 2009

#152: [wktraster] raster_columns out-db field should be an array
  Reporter:  pracine    |       Owner:  mloskot         
      Type:  defect     |      Status:  new             
  Priority:  low        |   Milestone:  WKTRaster Future
 Component:  wktraster  |     Version:  trunk           
Resolution:             |    Keywords:                  
Changes (by pracine):

  * priority:  high => low
  * milestone:  WKTRaster 0.1.6 => WKTRaster Future


 The problem is that out-db (actually offline in rt_api.c) is a per-band
 variable. So I'm trying to find in situations where we could end with a
 raster having one or many out-db bands and one or many in-db bands. Up to
 now the only case I found would be something like a ST_RasterFromBands(r1,
 r2, r3) function constructing a multi-band raster from raster columns
 originating from different tables. But we could decide that such a
 function always produce in-db rasters...

 I would say lets leave it a boolean until we get in a situation where we
 can not avoid having out-db and in-db bands at the same time in a raster.

 I set it to WKTRaster Future so we kepep track of it.

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

More information about the postgis-devel mailing list