[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:37 mloskot]:
 > Replying to [comment:31 pracine]:
 > > Replying to [comment:30 mloskot]:
 > > > Indeed, ST_SameAlignment can not be used as replacement for the
 regular_blocking flag.
 > >
 > > Agreed. But you don't need regular_blocking anymore right?
 >
 > This constraint is supposed to serve certain use-cases where a table
 stores regular grid of tiles, so a client application can recognize this
 kind of configuration quickly and easily, and treat it in such specific
 case. The tiles storage/cache is one of important use cases for PostGIS
 Raster. Please, with all my respect, don't be scientific-ignorant here
 guys and don't make PostGIS Raster just another GRASS, please.

 You will have to explain me what is "scientific-ignorant" here before I do
 anything... Is there a "proprietary-ignorant" or "company-stupid"
 equivalent? Why do people at Cadcord always have to do personnal attack
 when defending their cases? Is this British humor?

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