Select an operation to be performed on the table defined.

• 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 does not exist: The table is
  created if it does not exist.

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

• Clear table: The table content is deleted.
  You have the possibility to rollback the operation.

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

Action on data

On the data of the table defined, you can perform the following
operation:

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

• Update: Updates entries in the
  table.

• Delete: Deletes the entries which
  correspond to the entry flow.

Schema and Edit
schema

A schema is a row description, it defines the number of fields
to be processed and passed on to the next component. The schema is either
built-in or remotely stored in the Repository.

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.

Built-in: The schema is created and
stored locally for this component only. Related topic: see
Talend Studio User Guide.

Repository: The schema already exists
and is stored in the Repository, hence can be reused. Related topic: see
Talend Studio User Guide.

Where clauses for (for UPDATE and DELETE
only)

Enter a clause to filter the data to be updated or deleted
during the update or delete operations.

Default Table Name

Enter the default table name, between double quotation
marks.

Default Schema Name

Enter the default schema name,between double quotation
marks.

Table name from connection name is variable

Select this check box when the name of the connection to this component is
set to a variable, such as a context variable.

Use different table name

Select this check box to define a different output table name,
between double quotation marks, in the Table
name field which appears.

Mapping

Specify the metadata mapping file for the database
to be used. The metadata mapping file is used for the data type conversion
between database and Java. For more information about the metadata mapping,
see the related documentation for Type mapping.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job
level as well as at each component level.

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. 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.

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 check box is
cleared, if the component has this check box.

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 further information about variables, see
Talend Studio

User Guide.

Usage rule

tELTJDBCOutput is to be used along with
the tELTJDBCMap. Note that the Output
link to be used with these components must correspond strictly to the syntax of
the table name.

Note that the ELT components do not handle actual data flow but
only schema information.

Avoid using any keyword for the database as the table/column name or using any
special character in the table/column name. If you want to, you can enclose the
table/column name in a pair of " to see whether it
works. For example, when you want to use the keyword
number as an Oracle database column name, you can
have the Db Column value in the schema editor set to
"number". But note that this solution does not
always work.