MariaDB (MySQL-compatible) 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. |
Adding a Database Connection for MariaDB Spatial |
---|
Name
Entering a descriptive name allows you to easily find the connection in future workspaces. The following characters are not allowed in connection names: ^ \ / : * ? " < > | & = ' + % # Host
This specifies the machine running the MariaDB DBMS as either an IP address or host name. The database must have proper permissions and be set up to accept TCP/IP connections if connecting from a remote machine. Port
When connecting remotely, this specifies the TCP/IP port on which to connect to the DBMS service. The default port is 3306. Database
This field is automatically populated with the information specified in the Input Dataset field, which specifies the name of the MariaDB database. The database must exist in the DBMS. (This can be verified by executing the query SHOW DATABASES in the MariaDB query interpreter.) Username and Password
Enter the username and password to access the database, user account, or wherever authentication is required. |
Advanced
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.
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.
The number of features that FME places in each transaction before a transaction is committed to the database.
The default value is 1000.
You may want to execute some ad-hoc SQL prior to reading or writing a table. For example, it may be necessary to ensure that a view exists prior to attempting to read from it.
Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER
keyword, embedded at the beginning of the SQL block. The single character following this keyword will be used to split the SQL, 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 with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.
You may want to execute some ad-hoc SQL after reading or writing a set of tables. For example, it may be necessary to clean up a temporary view after writing to the database.
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, 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 with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.
If Yes, leading and trailing whitespace is stripped from field values.