[postgis-devel] [raster] About recent commit r8313

[Chris Hodgson]

Thanks for the clarification Bborie. I must have misread (I wish I had 
more time to pay attention to what is going on with raster development) 
but I thought I had read that, because of the lack of information about 
regular blocking (no constraint to check) it was going to be tossed. 
Sorry for the noise.

However, given that, it would be still nice to be able to work with the 
gdal blocking concept for best performance. Perhaps that will have to 
wait until there is time to sort out the problems you were having.

Chris

On 11-12-07 10:20 AM, dustymugs wrote:
>
> The regular_blocking isn't going anywhere.  The problem in the earlier 
> discussions was being able to enforce regular_blocking on a raster 
> column.  Since there is no way to enforce regular blocking at the 
> present time (and probably not until 2.1), the question was whether or 
> not to keep the regular_blocking column in the constraint-based 
> raster_columns view.
>
> Since there is no way to check that a raster column is regularly 
> blocked, the user is provided an method to set an informational 
> ("garbage") constraint indicating that a raster column is regularly 
> blocked.
>
> Once the logic is available to check that a raster column is regularly 
> blocked, the informational constraint will become a real table/column 
> constraint.
>
> -bborie
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel