Dynamic data import / export


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

Adapter PostgreSQL

The PostgreSQL Adapter is used for importing into (insert), exporting from (select) and replacing records (update) of a PostgreSQL database (8.x / 9.x) tables and views.


PostgreSQL Adapter, database properties
PostgreSQL Adapter, database properties

General tab

Connection and authentication

Server name or IP: This defines the host PostgreSQL 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 PostgreSQL database name that the data for the import/export shall be assigned to .

Port: The address of the port that the PostgreSQL server accepts requests from. Default = 5432.

User / Password: Enter into these fields the database User and Password to enable FlowHeater to authenticate its connection to the PostgreSQL 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.


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 PostgreSQL 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 PostgreSQL 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 PostgreSQL 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 PostgreSQL Adapter to store the change statements (Insert, Update) as an SQL script file with the specified name and path.


PostgreSQL Adapter, fields and data types
PostgreSQL Adapter, fields and data types

Fields / Data types tab

SQL: data 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 PostgreSQL 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.

Processing of PostgreSQL array fields: The PostgreSQL Adapter can only process arrays (at present) in conjunction with the STRING FlowHeater data type. The whole field/array contents is always read or replaced. The notation conforms to the general PostgreSQL array syntax, e.g. {"one", "two", "three"} or {1, 2, 3}

Field properties: How the properties of Primary Key and Auto Increment (Serial) 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. 
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!


Adapter settings in the Format tab

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