SQLite Writer Parameters

Enter the name of the SQLite3 database file.

• When unchecked (default) and a database already exists, then tables and features are written to the existing database.
• When checked, any existing database is deleted before writing begins. Checking this option also enables the Template File parameter.

If a database does not exist when writing begins, a new database is created.

This parameter is enabled when the Overwrite Existing Database option is checked.

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

• UPPERCASE – Change all feature type names to uppercase text.
• lowercase – Change all feature type names to lowercase text.
• None – Do not make changes to any feature type names.

• UPPERCASE – Change all attribute names to uppercase text.
• lowercase – Change all attribute names to lowercase text.
• None – Do not make changes to any attribute names.

Coordinate systems may be extracted from input feature data sources, may come predefined with FME, or may be user-defined. FME allows different output and input coordinate systems, and performs the required coordinate conversions when necessary.

For systems that know their coordinate system, the Coordinate System field will display Read from Source and FME will read the coordinate system from the source dataset. For most other input sources, the field will display Unknown (which simply means that FME will use default values). In most cases, the default value is all you'll need to perform the translation.

You can always choose to override the defaults and choose a new coordinate system. Select More Coordinate Systems from the drop-down menu to open the Coordinate System Gallery.

Changing a Reprojection

To perform a reprojection, FME typically uses the CS-MAP reprojection engine, which includes definitions for thousands of coordinate systems, with a large variety of projections, datums, ellipsoids, and units. However, GIS applications have slightly different algorithms for reprojecting data between different coordinate systems. To ensure that the data FME writes matches exactly to your existing data, you can use the reprojection engine from a different application.

To change the reprojection engine, Select Workspace Parameters > Spatial > Reprojection Engine. In the example shown, you can select Esri (but the selection here depends on your installed applications):

Specifies which SQL operations will be performed by default by this writer.

Supported modes are Insert, Update, Upsert, and Delete.

For detailed information on feature operations, see Feature Operation.

This setting enables the creation of tables without data features.

• No – Tables are only created when receiving data features.
• Yes – Tables are created without data features if possible.

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

The default value is 500.

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 SQL to Run editor help.

Tip  If you have enabled FME AI Assist, you can get help creating SQL queries. Click the AI Assist button to open the editor.

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 SQL to Run editor help.

Tip  If you have enabled FME AI Assist, you can get help creating SQL queries. Click the AI Assist button to open the editor.

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.