| 541 | | * There will be a flexible !ApplyRasterConstraint() function trying to apply a set of constraint on a table. As for any constraint, the constraints will be successfully applied only when all the rows of the table fulfil the constraint. The list of potential constraint applied by the C loader (using the !ApplyRasterConstraint function) and hence the list of column available in the raster_column view will be: srid int, scalex float8, scaley float8, width int, height int, alignment (align on a upperleft x and y), numberofband int, pixeltypes text[], nodatavalues float[] in addition to the 'r_table_catalog', 'r_table_schema', 'r_table_name' and 'r_column' columns. |
| 542 | | |
| 543 | | There is still discussion to know if extent as a geometry should be added to this list. Comments are welcomes. |
| | 541 | * There will be a flexible !ApplyRasterConstraint() function trying to apply a set of constraint on a table. As for any constraint, the constraints will be successfully applied only when all the rows of the table fulfil the constraint. The list of potential constraint applied by the C loader (using the !ApplyRasterConstraint function) and hence the list of column available in the raster_column view will be: srid int, scalex float8, scaley float8, width int, height int, alignment (align on a upperleft x and y), numberofband int, pixeltypes text[], nodatavalues float[] in addition to the 'r_table_catalog', 'r_table_schema', 'r_table_name' and 'r_column' columns. There is still discussion about if global extent as a geometry should be added to this list. Comments are welcomes. |
