<parameter>same_alignment=true</parameter></paramdef>
<paramdef choice="opt"><type>boolean </type>
- <parameter>regular_blocking=true</parameter></paramdef>
+ <parameter>regular_blocking=false</parameter></paramdef>
<paramdef choice="opt"><type>boolean </type>
<parameter>num_bands=true</parameter></paramdef>
<listitem><para><varname>num_bands</varname> number of bands</para></listitem>
<listitem><para><varname>pixel_types</varname> reads array of pixel types for each band ensure all band n have same pixel type</para></listitem>
- <listitem><para><varname>regular_blocking</varname> apply informational flag to denote all tiles are regularly blocked</para></listitem>
+ <listitem><para><varname>regular_blocking</varname> sets spatially unique (no two rasters can be spatially the same) and coverage tile (raster is aligned to a coverage) constraints</para></listitem>
<listitem><para><varname>same_alignment</varname> ensures they all have same alignment meaning any two tiles you compare will return true for. Refer to <xref linkend="RT_ST_SameAlignment" /></para></listitem>
<listitem><para><varname>srid</varname> ensures all have same srid</para></listitem>
<listitem><para>More -- any listed as inputs into the above functions</para></listitem>
SELECT AddRasterConstraints('public'::name, 'myrasters2'::name, 'rast'::name,'regular_blocking', 'blocksize');
-- get notice--
NOTICE: Adding regular blocking constraint
-INFO: The regular_blocking constraint is just a flag indicating that the column "rast" is regularly blocked. As no function exist yet to assert that a raster column is regularly blocked, it is up to the end-user to ensure that the column is truly regularly blocked.
-CONTEXT: PL/pgSQL function "addrasterconstraints" line 85 at assignment
NOTICE: Adding blocksize-X constraint
NOTICE: Adding blocksize-Y constraint</programlisting>
</refsection>
<parameter>same_alignment=true</parameter></paramdef>
<paramdef choice="opt"><type>boolean </type>
- <parameter>regular_blocking=true</parameter></paramdef>
+ <parameter>regular_blocking=false</parameter></paramdef>
<paramdef choice="opt"><type>boolean </type>
<parameter>num_bands=true</parameter></paramdef>
<term>-r </term>
<listitem>
<para>
- Set the regular blocking constraint. Only applied if -C flag is also used.
+ Set the constraints (spatially unique and coverage tile) for regular blocking. Only applied if -C flag is also used.
</para>
</listitem>
</varlistentry>
<para><varname>same_alignment</varname> A boolean that is true if all the raster tiles have the same alignment . Refer to <xref linkend="RT_ST_SameAlignment" /> for more details.</para>
</listitem>
<listitem>
- <para><varname>regular_blocking</varname> This is a true/false constraint flag set on the table to denote that the tiles do not overlap, are of the same alignment, pixel size, srid etc. It is not really validated but just taken as a given so should be used for informational. In the future we plan to properly constrain this so that this information is guaranteed to be right when it returns <varname>true</varname></para>
+ <para><varname>regular_blocking</varname> If the raster column has the spatially unique and coverage tile constraints, the value with be TRUE. Otherwise, it will be FALSE.</para>
</listitem>
<listitem>
<para><varname>num_bands</varname> The number of bands in each tile of your raster set. This is the same information as what is provided by <xref linkend="RT_ST_NumBands" /></para>
" if one or more rasters violate the constraint.\n"
" -x Disable setting the max extent constraint. Only applied if\n"
" -C flag is also used.\n"
- " -r Set the regular blocking constraint. Only applied if -C flag is\n"
- " also used.\n"
+ " -r Set the constraints (spatially unique and coverage tile) for\n"
+ " regular blocking. Only applied if -C flag is also used.\n"
));
printf(_(
" -T <tablespace> Specify the tablespace for the new table.\n"