[postgis-tickets] [PostGIS] #2777: [raster] Huge literal in enforce_max_extent_rast check constraint (was: 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):

 I'd keep the standard constraints for the sole purpose of enforcing what
 raster_columns is advertising. If there's nothing in raster_columns that
 depends on the "convex hull" of the raster, I'd rather avoid having it
 constrained by the AddRasterConstraint function.

 BTW, documentation for the function does not mention "extent" as being one
 of the constraints:
 http://postgis.net/docs/RT_AddRasterConstraints.html nor in the short or
 in the detailed description. Was it a recent introduction ?

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