tPostgresqlOutputBulk and tPostgresqlBulkExec components are used together to first output the
file that will be then used as parameter to execute the SQL query stated. These two
steps compose the tPostgresqlOutputBulkExec component,
detailed in a separate section. The interest in having two separate elements lies in the
fact that it allows transformations to be carried out before the data loading in the
database.
Component family |
Databases/Postgresql |
|
Function |
Executes the Insert action on the data provided. |
|
Purpose |
As a dedicated component, tPostgresqlBulkExec offers gains in performance |
|
Basic settings |
Property type |
Either Built-in or Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-in: No property data stored |
|
|
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component List click the NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing
For an example about how to share a database connection across Job levels, see |
|
DB Version |
List of database versions. |
|
Host |
Database server IP address |
|
Port |
Listening port number of DB server. |
|
Database |
Name of the database. |
|
Schema |
Name of the schema. |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
Table |
Name of the table to be written. Note that only one table can be |
|
Action on table |
On the table defined, you can perform one of the following
None: No operation is carried
Drop and create table: The table is
Create table: The table does not
Create table if not exists: The
Drop table if exists and create:
Clear table: The table content is
Truncate table: The table content |
|
File Name |
Name of the file to be loaded. WarningThis file is located on the machine specified by the URI in |
|
Schema and Edit |
A schema is a row description, it defines the number of fields to Since version 5.6, both the Built-In mode and the Repository mode are Click Edit schema to make changes to the schema. If the
|
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and When the schema to be reused has default values that are integers or functions, ensure that For more details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema. |
Advanced settings |
Action on data |
On the data of the table defined, you can perform:
Bulk Insert: Add multiple entries
Bulk Update: Make simultaneous |
|
Copy the OID for each row |
Retrieve the ID item for each row. |
|
Contains a header line with the names of each column in |
Specify that the table contains header. |
|
File type |
Select the type of file being handled. |
|
Null string |
String displayed to indicate that the value is null. |
|
Fields terminated by |
Character, string or regular expression to separate fields. |
|
Escape char |
Character of the row to be escaped. |
|
Text enclosure |
Character used to enclose text. |
|
Activate standard_conforming_string |
Activate the variable. |
|
Force not null for columns |
Define the columns nullability. Force not null: Select the check |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Usage |
This component is to be used along with tPostgresqlOutputBulk component. Used together, they |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. |
|
Limitation |
n/a |
For use cases in relation with tPostgresqlBulkExec,
see the following scenarios: