[postgis-devel] [PostGIS] #1319: [raster] Make raster_columns a constraint-based view, replace AddRasterColumn with ApplyRasterConstraints and expand # of constraints on raster columns

[PostGIS]

#1319: [raster] Make raster_columns a constraint-based view, replace
AddRasterColumn with ApplyRasterConstraints and expand # of constraints on
raster columns
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  dustymugs    
     Type:  task            |      Status:  assigned     
 Priority:  critical        |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by dustymugs):

 Replying to [comment:29 pracine]:
 > Replying to [comment:27 mloskot]:
 > > Replying to [comment:23 dustymugs]:
 > > > Instead of having the column "out_db", the column should be renamed
 to "all_in_db"
 > >
 > >
 > > Is it possible to have a raster partially "in_db" and partially
 "out_db". If it is not possible, "all_" prefix is superfluous.
 >
 > out-db is a band property so theoretically it is possible that one band
 is in-db and another band is out-db... This is why we need an array for
 out-db. But I would not set it as a constraint now as out-db is still
 inconsistently implemented.

 So, does this mean we should remove it from the view for now?  Maybe come
 back in the future when the out-of-db implementation is fully developed?

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