CN114116662A - Method, device and application for realizing dblink based on foreign data wrapper in OpenGauss database - Google Patents
Method, device and application for realizing dblink based on foreign data wrapper in OpenGauss database Download PDFInfo
- Publication number
- CN114116662A CN114116662A CN202111332968.0A CN202111332968A CN114116662A CN 114116662 A CN114116662 A CN 114116662A CN 202111332968 A CN202111332968 A CN 202111332968A CN 114116662 A CN114116662 A CN 114116662A
- Authority
- CN
- China
- Prior art keywords
- database
- dblink
- name
- remote
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Power Engineering (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the technical field of database operating systems and computer software, and particularly relates to a method, a device and application for realizing dblink based on an external data wrapper in an OpenGauss database. By the method, the OpenGauss database can obtain a dblink function similar to an Oracle database, and by creating the dblink of the remote database, the OpenGauss can access the data in the remote database table at any time like accessing the local database without creating a corresponding external table in the local database or paying attention to the table structure change of the remote database table, so that the access of the OpenGauss to the data of the remote database table is greatly facilitated, the use convenience and flexibility are improved, and the database maintenance cost is effectively reduced.
Description
Technical Field
The invention belongs to the technical field of database operating systems and computer software, and particularly relates to a method, a device and application for realizing dblink based on an external data wrapper in an OpenGauss database.
Background
In the information era, mass data are generated all the time, and with the increase of business association, mutual access and data transmission among databases are increasingly frequent.
OpenGauss is an open-source relational database management system, the kernel of which is derived from PostgreSQL, and the system is used as an open-source free database platform and aims to encourage community contribution and cooperation. At present, OpenGauss can access data in a remote database table through an external data wrapper, but for each table of a remote database to be accessed, a corresponding external table must be created in a local database, and when the table structure of the remote database table changes, a new external table matched with the local database needs to be re-created in the local database, so that the using process is complicated, the flexibility is poor, and the maintenance cost is high.
The dblink (database link) is a database link, data in the remote database table can be accessed at any time through the dblink local database, and a user does not need to create a corresponding external table in the local database and pay attention to table structure change of the remote database table. If the dblink can be realized by OpenGauss, the access to the remote database table data can be greatly facilitated, and the use convenience and flexibility of the database table data can be obviously improved.
Disclosure of Invention
In order to overcome the defects of complicated steps, poor flexibility and high maintenance cost when the OpenGauss database accesses the remote database table data through an external data wrapper, the invention provides a solution, the OpenGauss database can obtain a dblink function similar to an Oracle database by using the method, and the dblink of the remote database is created, so that the OpenGauss can access the data in the remote database table at any time as accessing the local database, a corresponding external table does not need to be created in the local database, and the table structure change of the remote database table does not need to be concerned, thereby greatly facilitating the access of the OpenGauss to the remote database table data, improving the use convenience and flexibility of the OpenGauss database, and reducing the maintenance cost of the database.
Firstly, the invention provides a method for realizing dblink based on an external data wrapper in an OpenGauss database, which comprises the following steps:
(1) dblink creation
And (3) creating grammar:
CREATE[PUBLIC]DATABASE LINK link_name
CONNECT TO user IDENTIFIED BY password[fdw_name]
USING(option'value'[,...])；
description of the parameters:
link _ name: the unique identification of the database link,
fdw _ name: the external wrapper used by the dblink is specified,
user/password: the username and password of the remote database server to which the connection is required,
option 'value' [, ]: populating the IP address and port number of the remote database server;
the implementation mode is as follows:
the method comprises the steps that the IP address and port number information of a remote server are pre-filled into a pg _ category.
(2) dblink use
The dblink accesses the tables of the remote database through the [ schema _ name ] table _ name @ dlink _ name syntax, such as: select from schema _ name table _ name @ dlink _ name; when the parser has recognized the dblink grammar,
a. querying a pg _ category dictionary table and a pg _ category dictionary table through a link _ name to obtain connection information, and connecting to a remote server;
b. and acquiring metadata of a corresponding table from a remote database server through [ schema _ name ] table _ name information, and writing the metadata into a pg _ catalog.
Further, according to the method for realizing dblink in the OpenGauss database, after the dblink is created, the table of the remote database is directly accessed according to the following mode:
(1) local database creation dblink based on oracle _ fdw
CREATE DATABASE LINK ora_dblink CONNECT TO system
IDENTIFIED BY'password'USING oracle_fdw(
dbserver'//172.16.103.104:1521/orcl'
)；
(2) When tbl _ test table exists in remote database, local database is directly accessed
SELECT*FROM tbl_test@ora_dblink。
Preferably, the external data encapsulator in the method for implementing dblink in the OpenGauss database of the present invention is composed of an analyzer, a planner, and an executor.
Further, the working steps of the external data wrapper are as follows:
(1) the analyzer creates a query tree of the input SQL according to definitions of external tables in a dictionary table of pg _ category.pg _ class and pg _ category.pg _ for _ table;
(2) connection information required by interaction between the external data wrapper and the remote database server is pre-stored in a dictionary table of pg _ catalog.pg _ foreign _ server and pg _ catalog.pg _ user _ mapping; the planner connects to the remote server according to the connection information stored in the dictionary tables of pg _ category.pg _ for _ server and pg _ category.pg _ user _ mapping;
(3) when the use _ remote _ estimate option is on, the planner will execute the EXPLAIN command to estimate the cost of each planned path;
(4) the planner creates a plain text SQL statement according to the planning tree;
(5) the executor sends the plain text SQL statement to a remote server and receives the result.
Further, in the working step (2) of the external data encapsulator, the IP address and port number information of the remote server are stored in advance in a pg _ catalog. pg _ foreign _ server dictionary table; the user name and password information of the remote server are stored in advance in a pg _ category.
Preferably, the method for implementing dblink in the OpenGauss database of the present invention comprises the following steps:
(1) dblink creation
And (3) creating grammar:
CREATE[PUBLIC]DATABASE LINK link_name
CONNECT TO user IDENTIFIED BY password[fdw_name]
USING(option'value'[,...])；
description of the parameters:
link _ name: the unique identification of the database link,
fdw _ name: the external wrapper used by the dblink is specified,
user/password: the username and password of the remote database server to which the connection is required,
option 'value' [, ]: populating the IP address and port number of the remote database server;
the implementation mode is as follows:
the method comprises the steps that the IP address and port number information of a remote server are pre-filled into a pg _ category.
(2) dblink use
a. Grammar phases
And modifying the grammar file to enable the grammar to identify the dblink table, providing table name information and the dblink name, and adopting the @ identifier:
[schema_name.]table_name@dlink_name；
parser phase of parser
According to dlink _ name provided by a grammar stage, inquiring a pg _ category, pg _ format _ server and pg _ category, pg _ user _ mapping dictionary table to obtain connection information, connecting the connection information to a remote database server, then according to [ schema _ name ] table _ name information, obtaining metadata of a corresponding table from the remote database server, and writing the metadata into the pg _ category, pg _ class and pg _ category, pg _ format _ table dictionary table; when the table field type of the remote database is different from the OpenGauss database, mapping the table field type of the remote database into an available local type; the method can be further optimized, after the table metadata is searched, the table metadata is compared with the locally retained metadata information, and if the table metadata is not changed, the table dictionary table of pg _ category, pg _ class and pg _ category, pg _ foreign _ table do not need to be updated;
c. stage of use
After the parser stage is completed, the external data wrapper obtains enough connection information, and direct access to the remote database can be realized through the external data wrapper.
In addition, the invention also relates to the application of the method for realizing dblink in the OpenGauss database in a database management or operation system.
On the other hand, the invention also provides a device for realizing dblink in the OpenGauss database based on the external data wrapper, wherein the device comprises a processor and a memory, the memory is used for storing programs, and the processor is used for running the programs so as to realize the method for realizing dblink in the OpenGauss database.
In conclusion, compared with the existing method for accessing the remote database table data by the OpenGauss database through the external data wrapper, the method for realizing dblink based on the external data wrapper in the OpenGauss database has the advantages of simple steps and the like. By the method, the OpenGauss database can obtain a dblink function similar to an Oracle database, and by creating the dblink of the remote database, the OpenGauss can access the data in the remote database table at any time like accessing the local database without creating a corresponding external table in the local database or paying attention to the table structure change of the remote database table, so that the access of the OpenGauss to the data of the remote database table is greatly facilitated, the use convenience and flexibility are improved, and the database maintenance cost is effectively reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention are briefly described below, it is obvious that the following drawings are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of the working steps of the external data wrapper of the present invention.
FIG. 2 is a schematic diagram of an implementation process of dblink implemented based on an external data encapsulator according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail and completely with reference to the following embodiments and accompanying drawings. It is to be understood that the embodiments described are merely illustrative of some, but not all, of the present invention and that the invention may be embodied or carried out in various other specific forms, and that various modifications and changes in the details of the specification may be made without departing from the spirit of the invention.
Also, it should be understood that the scope of the invention is not limited to the particular embodiments described below; it is also to be understood that the terminology used in the examples is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present invention.
Example 1: a method for realizing dblink based on an external data wrapper in an OpenGauss database comprises the following steps:
preparation of external data encapsulator (I) (see FIG. 1)
The external data wrapper consists of an analyzer, a planner and an executor, and the working steps are as follows:
(1) the analyzer creates a query tree of the input SQL according to definitions of external tables in a dictionary table of pg _ category.pg _ class and pg _ category.pg _ for _ table;
(2) connection information required by interaction between the external data wrapper and the remote database server is pre-stored in a dictionary table of pg _ category, pg _ foreign _ server and pg _ category, pg _ user _ mapping, specifically, an IP address and port number information of the remote server are pre-stored in the dictionary table of pg _ category, pg _ foreign _ server, and a user name and password information of the remote server are pre-stored in the dictionary table of pg _ category, pg _ user _ mapping; the planner connects to the remote server according to the connection information stored in the dictionary tables of pg _ category.pg _ for _ server and pg _ category.pg _ user _ mapping;
(3) when the use _ remote _ estimate option is on, the planner will execute the EXPLAIN command to estimate the cost of each planned path;
(4) the planner creates a plain text SQL statement according to the planning tree;
(5) the executor sends the plain text SQL statement to a remote server and receives the result.
(di) dblink creation
And (3) creating grammar:
CREATE[PUBLIC]DATABASE LINK link_name
CONNECT TO user IDENTIFIED BY password[fdw_name]
USING(option'value'[,...])；
description of the parameters:
link _ name: the unique identification of the database link,
fdw _ name: the external wrapper used by the dblink is specified,
user/password: the username and password of the remote database server to which the connection is required,
option 'value' [, ]: populating the IP address and port number of the remote database server;
the implementation mode is as follows:
the method comprises the steps that the IP address and port number information of a remote server are pre-filled into a pg _ category.
(iii) dblink use (see FIG. 2)
a. Grammar phases
And modifying the grammar file to enable the grammar to identify the dblink table, providing table name information and the dblink name, and adopting the @ identifier:
[schema_name.]table_name@dlink_name；
parser phase of parser
According to dlink _ name provided by a grammar phase, inquiring a pg _ category _ pg _ for _ server and a pg _ category _ pg _ user _ mapping dictionary table to obtain connection information, connecting the connection information to a remote database server (2.1 in the attached figure 2), then according to [ schema _ name ] table _ name information, obtaining metadata (2.2 in the attached figure 2) of a corresponding table from the remote database server, and writing the metadata into the pg _ category, pg _ class and pg _ category. When the table field type of the remote database is different from the OpenGauss database, mapping the table field type of the remote database into an available local type;
c. stage of use
After the parser stage is completed, the external data wrapper obtains enough connection information, and direct access to the remote database can be realized through the external data wrapper.
The above description is only an example of the present invention, and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, replacement, or the like that comes within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (8)
1. A method for realizing dblink based on an external data wrapper in an OpenGauss database is characterized by comprising the following steps:
(1) dblink creation
And (3) creating grammar:
CREATE[PUBLIC]DATABASE LINK link_name
CONNECT TO user IDENTIFIED BY password[fdw_name]
USING(option'value'[,...])；
description of the parameters:
link _ name: the unique identification of the database link,
fdw _ name: the external wrapper used by the dblink is specified,
user/password: the username and password of the remote database server to which the connection is required,
option 'value' [, ]: populating the IP address and port number of the remote database server;
the implementation mode is as follows:
the method comprises the steps that the IP address and port number information of a remote server are pre-filled into a pg _ category.
(2) dblink use
The dblink accesses the tables of the remote database through the [ schema _ name ] table _ name @ dlink _ name grammar, and when the parser recognizes the dblink grammar,
a. querying a pg _ category dictionary table and a pg _ category dictionary table through a link _ name to obtain connection information, and connecting to a remote server;
b. and acquiring metadata of a corresponding table from a remote database server through [ schema _ name ] table _ name information, and writing the metadata into a pg _ catalog.
2. The method for implementing dblink in OpenGauss database according to claim 1, wherein after creating dblink, the table of the remote database is directly accessed as follows:
(1) local database creation dblink based on oracle _ fdw
CREATE DATABASE LINK ora_dblink CONNECT TO system
IDENTIFIED BY'password'USING oracle_fdw(
dbserver'//172.16.103.104:1521/orcl'
)；
(2) When tbl _ test table exists in remote database, local database is directly accessed
SELECT*FROM tbl_test@ora_dblink。
3. The method for implementing dblink in OpenGauss database according to claim 1, wherein the external data wrapper is composed of an analyzer, a planner and an executor.
4. The method for implementing dblink in an OpenGauss database according to claim 3, wherein the external data wrapper comprises the following steps:
(1) the analyzer creates a query tree of the input SQL according to definitions of external tables in a dictionary table of pg _ category.pg _ class and pg _ category.pg _ for _ table;
(2) connection information required by interaction between the external data wrapper and the remote database server is pre-stored in a dictionary table of pg _ catalog.pg _ foreign _ server and pg _ catalog.pg _ user _ mapping; the planner connects to the remote server according to the connection information stored in the dictionary tables of pg _ category.pg _ for _ server and pg _ category.pg _ user _ mapping;
(3) when the use _ remote _ estimate option is on, the planner will execute the EXPLAIN command to estimate the cost of each planned path;
(4) the planner creates a plain text SQL statement according to the planning tree;
(5) the executor sends the plain text SQL statement to a remote server and receives the result.
5. The method for implementing dblink in OpenGauss database according to claim 4, wherein in the step (2), the IP address and port number information of the remote server are stored in advance in a pg _ catalog.pg _ foreign _ server dictionary table; the user name and password information of the remote server are stored in advance in a pg _ category.
6. The method for implementing dblink in OpenGauss database according to claim 1, wherein the method comprises the following steps:
(1) dblink creation
And (3) creating grammar:
CREATE[PUBLIC]DATABASE LINK link_name
CONNECT TO user IDENTIFIED BY password[fdw_name]
USING(option'value'[,...])；
description of the parameters:
link _ name: the unique identification of the database link,
fdw _ name: the external wrapper used by the dblink is specified,
user/password: the username and password of the remote database server to which the connection is required,
option 'value' [, ]: populating the IP address and port number of the remote database server;
the implementation mode is as follows:
the method comprises the steps that the IP address and port number information of a remote server are pre-filled into a pg _ category.
(2) dblink use
a. Grammar phases
And modifying the grammar file to enable the grammar to identify the dblink table, providing table name information and the dblink name, and adopting the @ identifier:
[schema_name.]table_name@dlink_name；
parser phase of parser
According to dlink _ name provided by a grammar stage, inquiring a pg _ category, pg _ format _ server and pg _ category, pg _ user _ mapping dictionary table to obtain connection information, connecting the connection information to a remote database server, then according to [ schema _ name ] table _ name information, obtaining metadata of a corresponding table from the remote database server, and writing the metadata into the pg _ category, pg _ class and pg _ category, pg _ format _ table dictionary table; when the table field type of the remote database is different from the OpenGauss database, mapping the table field type of the remote database into an available local type;
c. stage of use
After the parser stage is completed, the external data wrapper obtains enough connection information, and direct access to the remote database can be realized through the external data wrapper.
7. Use of the method of implementing dblink in an OpenGauss database as claimed in any of claims 1-6 in a database management or operating system.
8. The device for realizing dblink based on the external data wrapper in the OpenGauss database is characterized in that: the apparatus comprises a processor and a memory, the memory is used for storing a program, and the processor is used for running the program to realize the method for realizing dblink in OpenGauss database in any claim 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111332968.0A CN114116662B (en) | 2021-11-11 | 2021-11-11 | Method, device and use for implementing dblink based on external data wrapper in OpenGauss database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111332968.0A CN114116662B (en) | 2021-11-11 | 2021-11-11 | Method, device and use for implementing dblink based on external data wrapper in OpenGauss database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114116662A true CN114116662A (en) | 2022-03-01 |
| CN114116662B CN114116662B (en) | 2025-03-25 |
Family
ID=80378480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111332968.0A Active CN114116662B (en) | 2021-11-11 | 2021-11-11 | Method, device and use for implementing dblink based on external data wrapper in OpenGauss database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114116662B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120371901A (en) * | 2025-06-27 | 2025-07-25 | 天津南大通用数据技术股份有限公司 | Dblink access construction method under distributed transaction database |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6226649B1 (en) * | 1997-06-23 | 2001-05-01 | Oracle Corporation | Apparatus and method for transparent access of foreign databases in a heterogeneous database system |
| US20030065662A1 (en) * | 2001-08-13 | 2003-04-03 | Jasmin Cosic | Universal data management interface |
| CN103902565A (en) * | 2012-12-26 | 2014-07-02 | 阿里巴巴集团控股有限公司 | Method and device for determining data access relation |
| CN108431810A (en) * | 2015-10-23 | 2018-08-21 | 甲骨文国际公司 | proxy database |
| CN111026782A (en) * | 2019-12-25 | 2020-04-17 | 上海达梦数据库有限公司 | Method, device and equipment for optimizing remote database object and storage medium |
-
2021
- 2021-11-11 CN CN202111332968.0A patent/CN114116662B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6226649B1 (en) * | 1997-06-23 | 2001-05-01 | Oracle Corporation | Apparatus and method for transparent access of foreign databases in a heterogeneous database system |
| US20030065662A1 (en) * | 2001-08-13 | 2003-04-03 | Jasmin Cosic | Universal data management interface |
| CN103902565A (en) * | 2012-12-26 | 2014-07-02 | 阿里巴巴集团控股有限公司 | Method and device for determining data access relation |
| CN108431810A (en) * | 2015-10-23 | 2018-08-21 | 甲骨文国际公司 | proxy database |
| CN111026782A (en) * | 2019-12-25 | 2020-04-17 | 上海达梦数据库有限公司 | Method, device and equipment for optimizing remote database object and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120371901A (en) * | 2025-06-27 | 2025-07-25 | 天津南大通用数据技术股份有限公司 | Dblink access construction method under distributed transaction database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114116662B (en) | 2025-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8032544B2 (en) | Methods and apparatus for generating dynamic program files based on input queries that facilitate use of persistent query services | |
| US7895226B2 (en) | System and method for translating and executing update requests | |
| CN107463632A (en) | A kind of distributed NewSQL Database Systems and data query method | |
| US7979456B2 (en) | Method of managing and providing parameterized queries | |
| CN110134681B (en) | Data storage and query method and device, computer equipment and storage medium | |
| US8725760B2 (en) | Semantic terminology importer | |
| US7099727B2 (en) | Knowledge repository system for computing devices | |
| CN113254519B (en) | Access method, device, equipment and storage medium of multi-source heterogeneous database | |
| WO2008068114A1 (en) | Workflow processing system and method with federated database system support | |
| US20050060397A1 (en) | Method and system for managing a computer system | |
| US7509248B2 (en) | Generic persistence engine | |
| CN102355499B (en) | Cloud computing system | |
| CN116737113B (en) | Metadata catalog management system and method for mass scientific data | |
| CN110888878A (en) | Service-oriented main data management method and system | |
| CN115617922A (en) | Metadata management method and system for multimode database | |
| CN114116662A (en) | Method, device and application for realizing dblink based on foreign data wrapper in OpenGauss database | |
| US7707211B2 (en) | Information management system and method | |
| CN104503735B (en) | A method for verifying the consistency of standardized data exchange interfaces in power grid systems | |
| CN112506961A (en) | Method for improving data query efficiency | |
| CN114153438A (en) | API automatic generation system | |
| JPH1021125A (en) | System for managing location of distributed database system | |
| CN116339717B (en) | Data execution method, device, equipment and medium | |
| WO2025108191A1 (en) | Data query method, device, cluster and readable storage medium | |
| CN118939650A (en) | Data table management method and device | |
| CN105741087A (en) | Business flow import method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |