Dynamic data import / export

datenbank

simply more productive
Up to 10,000 records can be processed with the freeware version!

Adapter MySQL

The MySQL Adapter is used to import (insert), export (select) and amend (update) MySQL database tables and views. The Adapter supports MySQL Server Version 3.x and higher.

General tab

Connection and authentication

MySQL Adapter, database propertiesMySQL Adapter, database properties

Server name or IP: This defines the host MySQL Server that FlowHeater should connect to. As well as a URL specifying the host via DNS, a direct IP address can be used.

Database: Here you enter the name of the MySQL database or the catalog name that the data for the import/export shall be assigned to .

Port: The address of the port that the MySQL server accepts requests from. Default = 3306.

 User / Password: Enter into these fields the database User and Password to enable FlowHeater to authenticate its connection to the MySQL database. Important: The password is only stored if you check the "Save Password" option. If a password is saved it is stored in an encrypted form in the Definition data.

 

Common

Insert data: When this option is checked, SQL Insert statements are generated.

Ignore existing records: During an import and when this option is checked, records that already exist in the table are ignored.

Empty the table before importing: When this is checked you tell the MySQL Adapter to empty the contents of the table prior to running the import, effectively deleting all existing rows.

Update data: When this option is checked, SQL Update statements are generated. Note: If both the Insert and Update options are checked, the MySQL Adapter checks whether an SQL Update or Insert should be generated in each instance, by reference to the PrimaryKey. Tip: If you are certain there is only data to insert then avoid checking the Update option, as this will make the process significantly faster.

No updates or inserts to data, only generate an SQL script: When this option is checked, it signals the MySQL Adapter to make no inline changes to the database, but instead to store an SQL script with Insert and/or Update statements. This is useful for testing during development and for subsequent application to the database. If this option is checked you should also check the option below and enter the filename that the SQL statements are to be stored in.

Generate SQL script: This option instructs the MySQL Adapter to store the change statements (Insert, Update) as an SQL script file with the specified name and path.

Fields / Data types tab

SQL: MySQL Adapter, fields and data typesMySQL Adapter, fields and data typesdata available varies according to the side of the Adapter in use:

On the READ side: here you can choose from Tables and Views.
On the WRITE side: only Tables are available.

On the READ side you also have the possibility to enter complex SQL statements in the text field. Table joins must be defined by hand. In the second combo box the tables and views are listed that are available in the specified MySQL (catalog) database.

Fields: When you click the Load Schema button, information is retrieved from the database schema (field names, field sizes, data types, primary key, etc.) for the SQL statement above. The information about the fields is then loaded into the field list to the left of this button.
Note: The fields in the field list can be ordered in any sequence required. Fields that are not required can either be temporarily disabled here (tick removed) or simply deleted.

Field properties: How the properties of Primary Key and Auto Increment for the currently highlighted field are to be interpreted are adjusted. This information is only required on the WRITE side. No changes are needed here generally, since the correct information is usually obtained directly from the schema. Note: In versions of MySQL Server prior to version 5.0, Auto Increment fields are not automatically detected.
A PrimaryKey field is used in an Update to identify record that possibly exists.
Auto Increment fields are neither assigned nor amended in Insert/Update statements.
Warning: If you make changes here it can result in more than one record being updated with an Update!

Advanced tab

General

MySQL Adpater extented propertiesMySQL Adpater extented propertiesAutomatically strip spaces from the start and end of content: If you check this option an auto trim of whitespace characters will be carried out on STRING data types. This means that any spaces, tabs and line break characters are automatically removed from the leading and trailing parts of strings.

Use TRUNCATE TABLE (=quicker) instead of DELETE FROM: When the option “Empty the table before importing” under the General tab is checked “TRUNCATE TABLE” instead of “DELETE FROM” (=default) is used to empty the table content.

Connection timeout: Timeout in seconds while waiting for connection to be established. If no connection has been made after this period, then the import/export run is aborted.

Command timeout: Timeout in seconds while waiting for an SQL command to complete. By entering a zero value here, effectively disables the option altogether. In that case SQL commands will never timeout and are awaited endlessly. This option makes sense when you select massive data volumes from a database on the READ side and the MySQL Server takes a long time to prepare its result.

Use database transactions: This allows you to control how data is imported. According to the default settings MySQL Adapter uses a single “large” transaction to secure the entire import process. When importing extremely large volumes you may have to adapt transactional behavior to your needs using the “Run AutoCommit after writing every X records”.

Use UNICODE strings: When checked this option will force output of a prefix to the initial apostrophe. e.g. N’import value’ instead of ‘import value’.

Continue running in the face of SQL error occurs: This option allows you to instruct FlowHeater not to abort a run when it encounters an MySQL database error. Warning: This option should only be used in exceptional circumstances, because database inconsistencies could result.

Adapter settings in the Format tab

The use of the Format tab is described in detail under general information about the usage of Adapters

 

Examples

 

MySQL® is a registered trademark of MySQL AB