PostGIS Raster Writer Parameters
|
Database formats include a Database Connection parameter that defines and stores authentication information. For general information about sharing database connections, please see Note that Database Connection parameters differ slightly, depending on context and/or database format. |
|
Connection From the Connection parameter in a database format, you can do one of the following:
|
Database Connection
Select an existing PostgreSQL database connection, or Add Database Connection...
|
Add PostGIS/PostgreSQL Database Connection To define a new connection from the Connection parameter in a PostGIS Raster format, see the topic PostGIS Raster: Add Database Connection. |
Table Creation
Specifies the name of the column to be created that will hold the raster data when creating a new table.
If set to Yes, changes the case of attribute names to lowercase.
Advanced
No – The writer inserts data into the database using SQL INSERT statements.
Yes – The writer inserts data using the SQL COPY command, which yields better performance.
The number at which the writer will start writing features into the database. The writer skips the number of features in this parameter, and then it begins writing the features that follow.
Usually, the value specified is 0 (which is the default) – a non-zero value is usually only specified when a data load operation is being resumed after failing partway through.
The number of features that FME places in each transaction before a transaction is committed to the database.
If the parameter is set to 0, then the entire write operation occurs in a single transaction.
Default: 100
This parameter allows for the execution of SQL statements before writing to a table. For example, it may be necessary to clean up a table before attempting to write to it. The statements will be executed only when the first feature arrives at the writer.
For detailed information about SQL functions, click the corresponding menu item in the .
Available menu options depend on the format.
Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors ; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.
This parameter allows for the execution of SQL statements after a set of tables has been written. For example, it may be necessary to clean up a temporary view after creating it.
For detailed information about SQL functions, click the corresponding menu item in the .
Available menu options depend on the format.
Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors ; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

