SQLite Non-Spatial Writer Parameters

Database Connections
Connections store authentication information. For general information about sharing database connections, please see Using Database Connections. Note: Depending on context and/or database format, you might see different combinations of Database Connection parameters. Connection Select an existing connection, or Add Database Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users.

Database

Enter the name of the SQLite3 database file.

Overwrite Existing Database

If this option is unchecked (default) and a database already exists, then tables and features are written to the existing database.
If this option is checked, any existing database is deleted before writing begins.

If no database exists when writing begins, a new database is created.

Note: After a database is deleted, it cannot be recovered – all data is lost.

Template File

If a template file is specified, the destination file is replaced with a copy of the template before writing begins.

Writer Mode

Specifies which SQL operations will be performed by default by this writer. This default writer-level value can be overwritten at the feature type or table level.

INSERT: Allows for only INSERT operations.
UPDATE and DELETE: These writer modes can be overwritten at the feature type level.

Starting Feature

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 (this is the default) – a non-zero value is usually only specified when a data load operation is being resumed after failing partway through.

Features Per Transaction

The number of features that FME places in each transaction before a transaction is committed to the database.

The default value is 1000.

SQL to Run Before Write

This parameter allows for the execution of SQL statements before opening a table for writing. For example, it may be necessary to drop a constraint 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 SQL to Run editor help.

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.

SQL to Run After Write

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.