[postgis-tickets] [PostGIS] #2809: [raster] AddRasterConstraint does not check arguments upfront

[PostGIS]

#2809: [raster] AddRasterConstraint does not check arguments upfront
-------------------------+--------------------------------------------------
 Reporter:  strk         |       Owner:  dustymugs    
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.2.0
Component:  raster       |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------
 I was confused by AddRasterConstraint failing with a vague message "could
 not add any constraint".
 Improving the error messages with r12722 I found out I had a typo in the
 column name, but still the AddRasterConstraint function kept calling each
 constraint-specific method rather than immediately giving up.

 It would be nicer if the existance of the target table/column and its
 readability would be checked upfront instead, giving a more human-readable
 message on failure.

 Dunno how safe it would be to backport this (togheter with r12722) back
 till the 2.0 branch

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