[postgis-devel] [PostGIS] #1319: [raster] Make raster_columns a view and AddRasterColumn enforce more

[PostGIS]

#1319: [raster] Make raster_columns a view and AddRasterColumn enforce more
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  robe         
     Type:  task            |      Status:  new          
 Priority:  high            |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 So the importer will call something like populate_raster_columns() which
 will automatically determine which constraint (srid, scalex, scaley,
 bandtype) is applicable to a table? If one and only one raster do not
 satisfy the constraint the constraint is not applyed right?

 Maybe adding nodataValue and numberOfBand?

 What about the extent? Can not be a constraint but it can be determined by
 the view? Too slow?

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