[postgis-tickets] [PostGIS] #2777: [raster] Huge literal in enforce_max_extent_rast check constraint

[PostGIS]

#2777: [raster] Huge literal in enforce_max_extent_rast check constraint
--------------------+-------------------------------------------------------
 Reporter:  strk    |       Owner:  dustymugs
     Type:  defect  |      Status:  new      
 Priority:  medium  |   Milestone:           
Component:  raster  |     Version:  trunk    
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by strk):

 Robe: do you see issues with changing the enforce_max_extent_rast
 parameter to the envelope ?
 The documentation for raster_columns says: "extent This is the extent of
 all the raster rows in your raster set." so I'd have it computed using
 ST_Extent(raster) -- which does not exist, see #1662. I guess
 ST_Extent(rast::geometry) is the closest one, is that good enough for the
 sake of raster_columns ?

 Sorry if I insist on this ticket but whenever I have to look at a
 raster_columns entry I cant because the "extent" field fills up the whole
 screen... :/

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