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

 I suppose we could.  There is no property we can read from a raster to
 determine it is an overview raster though so we would therefore have to go
 by pure naming convention.

 e.g. a table is a raster over view if it's got a name like

 o_<anumber>_an_existing_raster_table  (where a number is the pyramid
 level)

 and it has a raster column

 I guess the benefit of that is if someone drops an over view table, it
 would automatically disappear from the raster_overview catalog view.


 How do people feel about going by naming conventions.  Right now its just
 raster2pgsql.py making overviews and it follows the saming naming
 convention each time so easy to parse out.

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