tPostgresqlOutput

Select the desired database type from the list and click Apply.

Either Built-in or Repository .

• Built-in: No property data stored centrally.
• Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Centralizing database metadata.

• Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

  Information noteNote: When a Job contains the parent Job and the child Job, do the following if you want to share an existing connection between the parent Job and the child Job (for example, to share the connection created by the parent Job with the child Job).

  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
  2. In the child level, use a dedicated connection component to read that registered database connection.

  For an example about how to share a database connection across Job levels, see Sharing a database connection.

• List of database versions.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Enter the name of the table to be written. Note that only one table can be written at a time

None: No operation is carried out.

Drop and create table: The table is removed and created again.

Create table: The table does not exist and gets created.

Create table if not exists: The table is created if it does not exist.

Drop table if exists and create: The table is removed if already exists and created again.

Clear table: The table content is deleted.

Truncate table: The table content is deleted. You don not have the possibility to rollback the operation.

Insert: Add new entries to the table. If duplicates are found, the Job stops.

Delete: Remove entries corresponding to the input flow.

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Dynamic schema.

This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually.

For more information, see Retrieving table schemas.

This component supports PostgreSQL vector data types. Use the VECTOR or Dynamic DB type in your schema column definition to store and then query vector embeddings. For more information about pgvector, read the Amazon documentation.

Select this checkbox to use the PostgreSQL database as a spatial database for geographic information system (GIS). When this checkbox is selected, two other check boxes are displayed:

• Create Spatial index: select this checkbox to create spatial index.
• Create geometry columns reference: select this checkbox to create geometry columns reference.

For more information about the PostgreSQL database, see http://www.postgresql.org/about/.

Select this checkbox and specify the alias of a data source created on the Talend Runtime side to use the shared connection pool defined in the data source configuration. This option works only when you deploy and run your Job in Talend Runtime .

This checkbox is not available when the Use an existing connection checkbox is selected.

Enter the alias of the data source created on the Talend Runtime side.

This field is available only when the Specify a data source alias checkbox is selected.

Select this option to use a schema other than the one specified by the component that establishes the database connection (that is, the component selected from the Component list drop-down list in Basic settings view). After selecting this option, provide the name of the desired schema in the Schema field.

This option is available when Use an existing connection is selected in Basic settings view.

This property is not available when the Use an existing connection check box in the Basic settings view is selected.

• Name: Type in the name of the schema column to be altered or inserted as new column
• SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data.
• Position: Select Before, Replace or After following the action to be performed on the reference column.
• Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

This checkbox will not work if you:

• type in 0 in the Commit every field, or
• select the Use an existing connection checkbox in the Basic settings view while the Auto Commit mode is activated in the database connection component.

Select this check box to display each step during processing entries in a database.

Select this checkbox to automatically convert the letters in all the column names and the table name to lowercase when you manipulate a table (such as inserting, deleting, or updating a table).

Select this check box to activate the batch mode for data processing.

Specify the number of records to be processed in each batch.

This field is available only when the Use batch mode check box is selected.

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

NB_LINE_UPDATED: the number of rows updated. This is an After variable and it returns an integer.

NB_LINE_INSERTED: the number of rows inserted. This is an After variable and it returns an integer.

NB_LINE_DELETED: the number of rows deleted. This is an After variable and it returns an integer.

NB_LINE_REJECTED: the number of rows rejected. This is an After variable and it returns an integer.

QUERY: the query statement processed. This is an After variable and it returns a string.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error checkbox is cleared, if the component has this checkbox.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

This component must be used as an output component. It allows you to carry out actions on a table or on the data of a table in a PostgreSQL database. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. For an example of tMysqlOutput in use, see Retrieving data in error with a Reject link.

This component supports PostgreSQL vector data types.

Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio.

The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.

Due to license incompatibility, one or more JARs required to use this component are not provided. You can install the missing JARs for this particular component by clicking the Install button on the Component tab view. You can also find out and add all missing JARs easily on the Modules tab in the Integration perspective of Talend Studio. For details, see Installing external modules.