tMysqlColumnList Standard properties - Cloud - 8.0

MySQL

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Database components (Integration) > MySQL components
Data Quality and Preparation > Third-party systems > Database components (Integration) > MySQL components
Design and Development > Third-party systems > Database components (Integration) > MySQL components
Last publication date
2024-02-29

These properties are used to configure tMysqlColumnList running in the Standard Job framework.

The Standard tMysqlColumnList component belongs to the Databases family.

The component in this framework is available in all Talend products.

Note: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see DB Generic components.

Basic settings

Database

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

Component list

Select the tMysqlConnection component in the list if more than one connection are planned for the current job.

Table name

Enter the name of the table.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Global Variables

Global Variables 

COLUMN_NAME: the name of the column currently iterated upon. This is a Flow variable and it returns a string.

DATA_TYPE: the data type of the column currently iterated upon. This is a Flow variable and it returns a string.

COLUMN_DEFAULT: the default value of the column currently iterated upon. This is a Flow variable and it returns a string.

IS_NULLABLE: nullability of the column currently uiterated upon. This is a Flow variable and it returns YES if the column allows NULL; otherwise, NO.

COLUMN_KEY: the key indicator of the column currently iterated upon. This is a Flow variable and it returns a string if the column is set to Key; otherwise it returns nothing.

CHARACTER_MAXIMUM_LENGTH: the maximum length in number of characters of the column currently iterated upon. This is a Flow variable, and it returns a numeric string for binary or character data types and NULL for other types.

NUMERIC_PRECISION: the data precision of the column currently iterated upon. This is a Flow variable, and it returns a numeric string for approximate numeric data, exact numeric data, integer data, or monetary data and NULL for other data types.

NUMERIC_SCALE: the scale in digits allowed in the column currently iterated upon. This is a Flow variable, and it returns a numeric string for approximate numeric data, exact numeric data, integer data, or monetary data and NULL for other data types.

NB_COLUMN: the number of columns iterated upon so far. 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 more information about variables, see Using contexts and variables.

Usage

Usage rule

This component is to be used along with Mysql components, especially with tMysqlConnection.

Dynamic settings

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.

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.