This section describes the directives that the Geodatabase writer module recognizes.
Each directive is prefixed by the current <WriterKeyword>_ when it is placed in a mapping file. By default, the <WriterKeyword> for the Geodatabase writer is the same as the <WriterType>.
IGNORE_FAILED_FEATURE_ENTRY
Required/Optional: Optional
Parameter: <ignore_failed_features>
Values: YES | NO
Default Value: NO
FME Workbench Parameter
Ignore Failed Features
Example:
GEODATABASE_SDE_IGNORE_FAILED_FEATURE_ENTRY YES
MAX_NUMBER_FAILED_FEATURES
Required/Optional: Optional
FME Workbench Parameter
Max Number of Features to Ignore
Example:
GEODATABASE_SDE_MAX_NUMBER_FAILED_FEATURES 100
DUMP_FAILED_FEATURES
Required/Optional: Optional
Values: YES | NO
FME Workbench Parameter
Dump Failed Features to File
Default: NO
FFS_DUMP_FILE
Required/Optional: Optional
Parameter: <ffs_dump_file>
Values: path and filename
FME Workbench Parameter
Failed Feature Dump Filename
Example:
GEODATABASE_MDB_FFS_DUMP_FILE "c:\user temp\bad features.ffs"
BEGIN_SQL{n}
Sometimes, you must execute some SQL statements prior to opening a table. For example, it may be necessary to ensure that a view exists before attempting to read from it.
Upon opening a connection to read from a database, the reader looks for the directive <ReaderKeyword>_BEGIN_SQL{n} (for n=0,1,2,...), and executes each such directive’s value as an SQL statement on the database connection.
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.
Required/Optional
Optional
FME Workbench Parameter
Begin SQL
END_SQL{n}
Sometimes you must execute some SQL statements after a set of tables has been read. For example, it may be necessary to clean up a temporary view after creating it in BEGIN_SQL.
Just before closing a connection on a database, the reader looks for the directive <ReaderKeyword>_END_SQL{n} (for n=0,1,2,...), and executes each such directive’s value as an SQL statement on the database connection.
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.
Required/Optional
Optional
FME Workbench Parameter
End SQL