[postgis-devel] [PostGIS] #1319: [raster] Make raster_columns a constraint-based view, replace AddRasterColumn with ApplyRasterConstraints and expand # of constraints on raster columns

[PostGIS]

#1319: [raster] Make raster_columns a constraint-based view, replace
AddRasterColumn with ApplyRasterConstraints and expand # of constraints on
raster columns
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  dustymugs    
     Type:  task            |      Status:  assigned     
 Priority:  critical        |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 Replying to [comment:30 mloskot]:
 > Replying to [comment:28 pracine]:
 > > Replying to [comment:26 mloskot]:
 > > > Replying to [comment:22 dustymugs]:
 > > > > I believe the column "regular_blocking" should be renamed to
 "same_alignment"
 > > > > as it is an analog to ST_SameAlignment.
 > > >
 > > > AFAICT from the current docs on ST_SameAlignment, the
 regular_blocking is
 > > > not the same concept.
 > > >
 > > > The regular_blocking flag indicates if tiles in a table/coverage
 form a
 > > > regular rectangular grid, or not.
 > >
 > > samealignment is necessary but not sufficient. Regularlyblocked also
 needs
 > > samewidth, sameheight, hasnogaps and hasnooverlaps.
 >
 > Indeed, ST_SameAlignment can not be used as replacement for the
 regular_blocking flag.

 Agreed. But you don't need regular_blocking anymore right? We are not
 planning to set this constraint, right Bborie?

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