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. This includes Name and Writer Name. From here, you can also control Dynamic Properties.
These parameters apply only to a selected feature type, not to the entire writer.
Tip: If a feature type parameter listed here conflicts with a writer-level parameter, then the writer parameter will be ignored and this feature type parameter will be used.
Table Settings: General
Writer Mode
- INSERT: Allows for only INSERT operations.
- UPDATE and DELETE: These writer modes can be overwritten at the feature type levels.
- INHERIT_FROM_WRITER: Takes the value from the writer level and does not override it at the feature type level.
Drop Table
If the table exists by this name, it should be dropped and recreated before any features are written to it.
Truncate Table
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.
Table Type
The type of table to be created. The valid values for the type may include one or all of the values listed below:
- MYISAM
- InnoDB
- MEMORY
- BDB
- CSV
- ARCHIVE
- MERGE
- NDB
- FEDERATED
Please refer to MySQL documentation for further information on these table types.
Create Spatial Index
Indicates whether or not a spatial index is to be created as part of the data writing. Valid choices are Yes or No.
Table Settings: Spatial
Spatial Column
This parameter specifies the name of the column to be created that will hold the geometry when creating a new MySQL 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
Operations Per SQL Statement
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.