To access feature type parameters, click the gear icon on a feature type in the workspace to open the Feature Type Parameter Editor. To always display the editor in Workbench, you can select View > Windows > Parameter Editor.
All feature types share similar General parameters, which may include the Feature Type Name, Reader or Writer Name, and Geometry.
In most Writer Feature Type parameter dialogs, you can also control Dynamic Schema Definitions. Some database formats accept a Table Qualifier prefix on the output table feature type.
See Editing Writer Feature Types for more information.
Table Settings: General
- INHERIT_FROM_WRITER (default): Takes the value from the writer level and does not override it at the feature type level.
- INSERT: Allows for only INSERT operations.
- UPDATE and DELETE: These writer modes can be overwritten at the feature type levels.
If the table exists by this name, it should be dropped and recreated before any features are written to it.
If the table exists by this name, it should be truncated before any features are written to it.
Table Creation Parameters
The parameters in this section take effect only when FME creates a table.
The type of table to be created. The valid value for the type is:
Please refer to MySQL documentation for further information on table types.
Table Settings: Spatial
This parameter specifies the name of the column to be created that will hold the geometry when creating a new table. If this value is left blank, no geometry column will be created and an attribute only table will be written.
Note: This may invalidate other geometry-related parameters.
Table Settings: Advanced
If set to 1, insert data will be bound (packed efficiently, with statement reuse), and sent every feature.
Any value N > 1 will cause inserts to be batched without statement reuse and executed every N statements.
In general, N=1 will result in fewer bytes transmitted over the network, but more round-trips than a higher N. Experimentation may be required to determine which value will offer the best performance for a given scenario.
This parameter is ignored for UPDATE and DELETE modes, where statements are always executed singly.