openGauss Data Connection

Version

Application Scenario

FineDataLink supports connection to openGauss data sources, with the following functions available: data reading and writing using Scheduled Task and Database Table Management.

Supported Data Type

The following data types are supported: numeric, monetary, boolean, character, binary, date/time, geometric, network address, bit-string, text search, UUID, JSON/JSONB, HLL data, range, object identifier, Pseudo, data types supported by column-store tables, XML, data types used by Ledger databases, and SET.

For details about the above data types, see Data Types.

openGauss supports implicit conversion between certain data types. For specific conversion relationships, see PG_CAST.

Prerequisite

For details, see Overview of Data Connection.

Version and Driver

Connection Information Collection

Collect the following information before connecting FineDataLink to the database.

• IP address and port number of the database server

Note:

The host name can contain numbers, letters, underscores (_), hyphens (-), and periods (.) only.

• Database name

• Username and password of the database

Note:

The user account used to configure the data connection must possess the following privileges: CREATE, DELETE, ALTER, UPDATE, SELECT, INSERT, and INDEX.

• Schema of the database to be connected

Procedure

For details about data connection creation, see Data Source Creation and Management.

Note that when configuring the data connection, you must select Custom from the drop-down list of  Driver and select the driver mentioned in the "Version and Driver" section of this document.

1. After configuring the data source, you can use it in Scheduled Task. For details, see Overview of Scheduled Task.

2. After configuring the data source, you can use it under Data Management > Database Table Management. For details, see Database Table Management.

3. Under System Management > General Configuration, the Auto Table Creation Configuration function is available for this data source, while the Field Mapping Rule function is not.