CN115309986A - System and method for mapping table of management interface - Google Patents
System and method for mapping table of management interface Download PDFInfo
- Publication number
- CN115309986A CN115309986A CN202210927641.6A CN202210927641A CN115309986A CN 115309986 A CN115309986 A CN 115309986A CN 202210927641 A CN202210927641 A CN 202210927641A CN 115309986 A CN115309986 A CN 115309986A
- Authority
- CN
- China
- Prior art keywords
- mapping table
- interface
- metadata
- statement
- module
- 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.)
- Pending
Links
- 238000013507 mapping Methods 0.000 title claims abstract description 159
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000005457 optimization Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 claims description 6
- 238000004364 calculation method Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 13
- 238000001914 filtration Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
Abstract
The invention provides a system and a method for managing a mapping table of an interface. The method comprises the following steps: executing a mapping table establishing program by a processor to establish a mapping table corresponding to an interface specification, and storing the mapping table in a storage device, wherein the interface specification corresponds to an interface; and executing, by the processor, a mapping table lookup procedure corresponding to the mapping table to receive the customer data from the consumer electronic device through the interface.
Description
Technical Field
The present invention relates to software system technology, and is especially system and method of managing interface mapping table.
Background
At present, when a user wants to query client data from an interface, since the client data from the interface is usually confidential/sensitive data, it is generally necessary to receive/store the client data completely before the query is executed, and therefore, it is difficult to ensure the security of the client data.
Disclosure of Invention
The invention aims at a system and a method for managing a mapping table of an interface, which can improve the safety of client data and the efficiency of data filtering/query.
According to an embodiment of the present invention, a system for managing a mapping table of an interface of the present invention includes a processor and a storage device. The storage device is coupled with the processor, wherein the processor executes a mapping table establishing program to establish a mapping table corresponding to the interface specification, and stores the mapping table in the storage device, wherein the interface specification corresponds to the interface; the processor executes a mapping table lookup procedure corresponding to the mapping table to receive customer data from the consumer electronic device via the interface.
According to an embodiment of the present invention, a method of managing a mapping table of an interface of the present invention includes: executing a mapping table establishing program by a processor to establish a mapping table corresponding to an interface specification, and storing the mapping table in a storage device, wherein the interface specification corresponds to an interface; and executing, by the processor, a mapping table lookup procedure corresponding to the mapping table to receive the customer data from the consumer electronic device through the interface.
Based on the above, the system and method for managing the mapping table of the interface according to the present invention can establish the mapping table corresponding to the interface specification. After the mapping table lookup procedure is performed, customer data may be received through the interface. Further, by performing data filtering/querying at the interface, the present invention can eliminate the need to receive complete client data (i.e. complete confidential/sensitive data of the client) from the client electronic device, thereby improving the security of the client data and the efficiency of data filtering/querying.
In order to make the aforementioned and other features and advantages of the invention more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
FIG. 1 is a schematic diagram of a system for managing mapping tables for interfaces in accordance with an embodiment of the present invention;
FIG. 2 is a flow diagram of a method of managing a mapping table of an interface according to an embodiment of the invention;
FIG. 3 is a schematic diagram of an interface specification of an embodiment of the present invention;
FIG. 4 is a diagram of a mapping table creation statement in accordance with an embodiment of the present invention;
FIG. 5 is a schematic diagram of an interface statement of an embodiment of the invention;
FIG. 6 is a diagram of a mapping table query statement, according to an embodiment of the invention;
FIG. 7 is a diagram of an optimized interface query statement in accordance with an embodiment of the present invention.
Description of the reference numerals
100: a system for managing a mapping table of an interface;
110: a processor;
120: a storage device;
121: a coordination module;
122: an analysis module;
123: an execution module;
124: a metadata database;
200: an interface;
300: a consumer electronic device;
400: a consumer electronic device;
s210, S220, step;
31. 32, data;
311. 321, customer name;
312. 322, employee name;
313. 323, quantity;
314. 324, a tenant;
401. 402, 403, 404 metadata;
40. 60, mapping table name;
501. 502, 503, 504, mapping relation;
at 61, the metadata is to be queried.
Detailed Description
Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.
FIG. 1 is a diagram of a system 100 for managing mapping tables for interfaces, in accordance with an embodiment of the present invention. Referring to fig. 1, system 100 includes a processor 110 and a storage device 120. The storage device 120 is coupled to the processor 110. The system 100 is, for example, a federated query system, as will be further explained below. In the embodiment, the system 100 may be communicatively connected to an Interface (API) 200, and the Interface 200 may be communicatively connected to the consumer electronic device 300. In addition, the system 100 may be communicatively coupled to the consumer electronic device 400.
In the present embodiment, the Processor 110 may include a Central Processing Unit (CPU), or other Programmable general purpose or special purpose Microprocessor (Microprocessor), digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), programmable Logic Device (PLD), other similar Processing Circuits, or a combination thereof. The storage device 120 may include a Memory (Memory) and/or a database (database), wherein the Memory may be, for example, a Non-Volatile Memory (NVM). The storage device 120 may store the relevant programs, modules, systems or algorithms for implementing the embodiments of the present invention, so as to be accessed and executed by the processor 110 to implement the relevant functions and operations described in the embodiments of the present invention. In the present embodiment, the storage device 120 may store a coordination module 121, a parsing module 122, an execution module 123, and a metadata database 124, whose functions will be described later.
FIG. 2 is a flow diagram of a method of managing a mapping table of an interface according to an embodiment of the invention. Referring to fig. 1 and 2, the system 100 of fig. 1 may perform the following steps S210 and S220. In step S210, the processor 110 may execute a mapping table establishing program to establish a mapping table corresponding to an interface specification corresponding to the interface 200, and store the mapping table in the storage device 120. At step S220, the processor 110 may execute a mapping table query routine corresponding to the mapping table to receive the customer data from the consumer electronic device 300 through the interface 200. In other words, after performing step S220, the processor 110 can utilize the mapping table (corresponding to the interface specification) to receive the customer data from the consumer electronic device 300 through the interface 200 without receiving complete customer data (i.e., complete confidential/sensitive data of the customer) from the consumer electronic device 300. As will be further explained below.
It should be noted that the user operating the consumer electronic device 400 may obtain the interface specification from the customer operating the consumer electronic device 300 before requesting the system 100 to execute the mapping table creation program. FIG. 3 is a diagram illustrating an interface specification according to an embodiment of the invention. The interface specification shown in fig. 3 may include data 31 and data 32. Data 31 and data 32 are, for example, transaction data of different employees with a particular customer. In detail, data 31 may include customer name 311, employee name 312, quantity 313, and tenant 314. On the other hand, data 32 may include customer name 321, employee name 322, quantity 323, and tenant 324. Quantity 313 is, for example, the quantity of the employee's transaction with the customer name 311 for the employee name 312. On the other hand, the quantity 323 is, for example, the quantity of the employee's transaction of the employee name 322 with the customer name 321.
The mapping table establishing procedure in step S210 will be further described below. It should be noted that, although the following embodiments are described by using specific codes, the present invention is not limited thereto.
First, the coordination module 121 may connect to the consumer electronic device 400 using Java Database Connectivity (JDBC). In other words, a user may operate consumer electronic device 400 to connect to system 100 using Java database connection techniques. After the system 100 is connected to the consumer electronic device 400, the coordination module 121 may receive a mapping table establishment statement from the consumer electronic device 400. FIG. 4 is a diagram of a mapping table establishment statement according to an embodiment of the invention. In detail, the mapping table creation statement may include metadata 401, 402, 403, and 404 of the mapping table (to be created by the user). The mapping table creation statement may also include the mapping table name 40 (of the mapping table that the user wants to create).
Next, the coordination module 121 may determine whether the metadata database 124 stores a mapping table. In detail, the coordination module 121 may determine whether the metadata repository 124 already stores the same mapping table as the mapping table name 40. When the coordination module 121 determines that the metadata database 124 already stores the same mapping table as the mapping table name 40, the coordination module 121 may transmit a mapping table creation failure message to the consumer electronic device 400 and terminate the mapping table creation process (without performing the mapping table query process of the subsequent step S220).
On the other hand, when the coordination module 121 determines that the metadata repository 124 does not store the mapping table (identical to the mapping table name 40), the parsing module 122 may determine whether the mapping table creation statement is legal. When the parsing module 122 determines that the mapping table establishment statement is not legal (e.g., the syntax of the mapping table establishment statement shown in fig. 4 has an error), the coordination module 121 may transmit a mapping table establishment failure message to the consumer electronic device 400, and terminate the mapping table establishment procedure (without performing the mapping table query procedure in the following step S220).
On the other hand, when the parsing module 122 determines that the mapping table creating statement is legal, the coordination module 121 may store the metadata 401, the metadata 402, the metadata 403, the metadata 404, and the interface statements corresponding to the metadata in the metadata database 124. FIG. 5 is a diagram of an interface statement according to an embodiment of the invention. Please refer to fig. 3, fig. 4 and fig. 5. The interface statement shown in fig. 5 includes a mapping between the metadata of fig. 4 and the interface specification of fig. 3. For example, the interface statements shown in fig. 5 include mapping 501 (between metadata 401 and customer name 311 and customer name 312), mapping 502 (between metadata 402 and employee name 312 and employee name 322), mapping 503 (between metadata 403 and quantity 313 and quantity 323), and mapping 504 (between metadata 404 and tenants 314 and 324). Further, since the interface sentence shown in fig. 5 includes "? tenant =10001&offset =0&limit =1 ″, and in the mapping table query program of step S220 of the subsequent fig. 2, the metadata 404 (i.e., "tenant _ id") will be used to perform query optimization. This will be further explained later. It should be noted that the coordination module 121 may further store the mapping table name 40 of the mapping table in the metadata database 124.
After the coordination module 121 stores the metadata (e.g., the metadata 401, 402, 403, and 404 shown in fig. 4), the interface statement corresponding to the metadata (e.g., the interface statement shown in fig. 5), and the mapping table name of the mapping table (e.g., the mapping table name 40 shown in fig. 4) in the metadata repository 124, the coordination module 121 may transmit a mapping table creation success message to the consumer electronic device 400 to notify the user operating the consumer electronic device 400 that the system 100 has successfully created the mapping table. The mapping table establishment success information may include the above-mentioned metadata, an interface statement corresponding to the metadata, and a mapping table name of the mapping table.
Please refer back to fig. 2. After the mapping table establishing procedure in step S210 is performed, the processor 110 may perform the mapping table querying procedure in step S220. The mapping table query procedure will be further explained below.
First, the coordination module 121 may connect to the consumer electronic device 400 using Java database connection technology. In other words, a user may operate consumer electronic device 400 to connect to system 100 using Java database connection techniques. After the system 100 is connected to the consumer electronic device 400, the coordination module 121 may receive a mapping table query statement from the consumer electronic device 400, wherein the mapping table query statement includes a mapping table name and metadata to be queried in the metadata. FIG. 6 is a diagram of a mapping table query statement, according to an embodiment of the invention. Please refer to fig. 3, fig. 4, fig. 5 and fig. 6. The mapping table query statement may include a mapping table name 60 (of the mapping table the user wants to query) and includes metadata 61 to query.
Then, the coordination module 121 may obtain the mapping table (e.g., the mapping table of the mapping table name 40 shown in fig. 4) from the metadata database 124 by using the mapping table name 60 (of the mapping table to be queried by the user), obtain the interface statement by using the metadata (e.g., obtain the interface statement shown in fig. 5 by using the metadata 401, the metadata 402, the metadata 403, and the metadata 404 of the mapping table name 40 shown in fig. 4), and obtain the interface query statement corresponding to the metadata to be queried ("cust _ name" and "smart _ id") by using the interface statement (e.g., obtain the interface query statement corresponding to the metadata to be queried 61 by using the interface statement shown in fig. 5).
Further, the parsing module 122 may perform syntax checking on the interface query statement and perform query optimization on the interface query statement to obtain an optimized interface query statement. In an embodiment, query optimization may include a predicate pushdown technique. FIG. 7 is an example of an optimized interface query statement obtained by parsing module 122. In detail, as explained in the previous embodiments, since the metadata 404 ("tent _ id") can be used to perform query optimization, the parsing module 122 can use the metadata 404 ("tent _ id") as a query condition for predicate pushdown techniques. In other words, the present invention will perform data filtering/querying at the interface 200 using the metadata 404. In detail, after the parsing module 122 obtains an optimized interface query statement (e.g., the optimized interface query statement shown in fig. 7), the execution module 123 may receive the customer data from the customer electronic device 300 through the interface 200 by using the optimized interface query statement. That is, the execution module 123 may use the optimized interface query statement as an interface query condition of the interface 200 to call the interface 200. By performing data filtering/querying at a location (interface 200) that is close to the data source, the present invention can eliminate the need to receive complete client data (i.e., complete confidential/sensitive data of the client) from the consumer electronic device 300, thereby improving the security of the client data and the efficiency of data filtering/querying.
After the execution module 123 receives the client data from the consumer electronic device 300 through the interface 200, the execution module 123 can store the client data in the storage device 120. Next, the execution module 123 may perform a summary calculation on the customer data to obtain a summary result. Table 1 below is one example of a summary result. In the above embodiment, since the mapping table query statement shown in fig. 6 includes the metadata 61 to be queried ("list _ name = 'east field'," content _ id =10001 "), and the interface statement shown in fig. 5 includes the mapping relation 501 (" list _ name: list ") and the mapping relation 504 (" content _ id: content "), and the interface specification shown in fig. 3 includes the data 31 (" list ": east field", "employee": king caption "," amount ":8000," content ": 10001") and the data 32 ("list": east field "," employee ": zhang", "amount":9000, "content": 10001 "), the client data received from the client electronic device 300 will include the data 31 and the data 32. Further, since the mapping table query statement shown in fig. 6 indicates summation (sum), the execution module 123 may perform a summary calculation on the number 313 of data 31 and the number 323 of data 32 to obtain a summary result shown in table 1 below.
Table 1 (an example of the summary results)
cust_name | sum(sale_amt) |
Dongdou (Dongdou) | 17000 |
After obtaining the aggregated results, the coordination module 121 may transmit the aggregated results to the consumer electronic device 400.
It is noted herein that system 100 may be a federated query system. In detail, as illustrated in the previous embodiment, the source of the queried customer data of the system 100 may be data from the interface 200. In this regard, the system 100 may perform federated queries on data from the interface 200, as well as on data from other sources (e.g., a general database).
In summary, the system and method for managing the mapping table of the interface according to the present invention can establish the mapping table corresponding to the interface specification. After the mapping table lookup procedure is executed, customer data may be received through the interface. Further, by performing data filtering/querying at the interface, the present invention can eliminate the need to receive complete customer data (i.e. complete confidential/sensitive data of the customer) from the consumer electronic device, thereby improving the security of the customer data and the efficiency of data filtering/querying.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (20)
1. A system for managing a mapping table for an interface, comprising:
a processor; and
a storage device coupled to the processor, wherein
The processor executes a mapping table establishing program to establish a mapping table corresponding to an interface specification, and stores the mapping table in the storage device, wherein the interface specification corresponds to an interface;
the processor executes a mapping table lookup procedure corresponding to the mapping table to receive customer data from the consumer electronic device via the interface.
2. The system of claim 1, wherein the storage device stores a coordination module and a resolution module, and the storage device stores a metadata base, wherein the mapping table creation procedure comprises:
the coordination module receiving a mapping table establishment statement from a consumer electronic device; and
when the coordination module judges that the metadata base does not store the mapping table, the analysis module judges whether the mapping table establishment statement is legal or not.
3. The system of claim 2, wherein the mapping table creation statement includes metadata for the mapping table, and wherein the mapping table creator further comprises:
when the analysis module judges that the mapping table establishing statement is legal, the coordination module stores the metadata and the interface statement corresponding to the metadata in the metadata database; and
the coordination module transmits mapping table establishment success information to the consumer electronic device.
4. The system of claim 2, wherein the mapping table builder further comprises:
the coordination module is connected to the consumer electronic device using java database connection technology.
5. The system of claim 1, wherein the storage device stores a coordination module and the storage device stores a meta database, wherein the meta database stores a mapping table name of the mapping table and metadata of the mapping table and stores an interface statement corresponding to the metadata, wherein the mapping table query procedure comprises:
the coordination module receives a mapping table query statement from a consumer electronic device, wherein the mapping table query statement comprises the mapping table name and metadata to be queried in the metadata; and
the coordination module obtains the mapping table from the metadata base by using the mapping table name, obtains the interface statement by using the metadata, and obtains an interface query statement corresponding to the metadata to be queried by using the interface statement.
6. The system of claim 5, wherein the storage device further stores a parsing module and an execution module, wherein the mapping table query procedure further comprises:
the analysis module executes syntax check on the interface query statement and executes query optimization on the interface query statement to obtain the optimized interface query statement; and
the execution module receives the customer data from the consumer electronic device through the interface using the optimized interface query statement.
7. The system of claim 6, the query optimization comprising a predicate push down technique.
8. The system of claim 5, wherein the mapping table querying routine further comprises:
the coordination module is connected to the consumer electronic device using java database connection technology.
9. The system of claim 1, wherein the storage device stores a coordination module and an execution module, wherein
The execution module stores the customer data in the storage device;
the execution module performs summary calculations on the customer data to obtain summary results;
the coordination module transmits the summary result to a consumer electronic device.
10. The system of claim 1, wherein the system is a federal query system.
11. A method for managing a mapping table of an interface, adapted to a system including a processor and a storage device, wherein the method comprises:
executing, by the processor, a mapping table establishing program to establish a mapping table corresponding to an interface specification, and storing the mapping table in the storage device, wherein the interface specification corresponds to an interface; and
executing, by the processor, a mapping table lookup procedure corresponding to the mapping table to receive customer data from the consumer electronic device through the interface.
12. The method of claim 11, wherein the storage device stores a coordination module and a resolution module, and the storage device stores a metadata database, and wherein the mapping table creating procedure comprises:
receiving, by the coordination module, a mapping table establishment statement from a consumer electronic device; and
when the coordination module judges that the metadatabase does not store the mapping table, the analysis module judges whether the mapping table establishing statement is legal or not.
13. The method of claim 12, wherein the mapping table creation statement includes metadata for the mapping table, and wherein the mapping table creator further comprises:
when the analysis module judges that the mapping table establishing statement is legal, the coordination module stores the metadata and the interface statement corresponding to the metadata in the metadata database; and
and transmitting mapping table establishment success information to the consumer electronic device by the coordination module.
14. The method of claim 12, wherein the mapping table builder further comprises:
connecting to the consumer electronic device by the coordination module using java database connection technology.
15. The method of claim 11, wherein the storage device stores a coordination module and the storage device stores a metadata database, wherein the metadata database stores mapping table names of the mapping tables and metadata of the mapping tables and stores interface statements corresponding to the metadata, and wherein the mapping table query procedure comprises:
receiving, by the coordination module, a mapping table query statement from a consumer electronic device, wherein the mapping table query statement includes the mapping table name and metadata to be queried in the metadata; and
and obtaining, by the coordination module, the mapping table from the metadata base using the mapping table name, obtaining the interface statement using the metadata, and obtaining an interface query statement corresponding to the metadata to be queried using the interface statement.
16. The method of claim 15, wherein the storage device further stores a parsing module and an execution module, wherein the mapping table query procedure further comprises:
performing, by the parsing module, syntax checking on the interface query statement and performing query optimization on the interface query statement to obtain an optimized interface query statement; and
receiving, by the execution module, the customer data from the consumer electronic device through the interface using the optimized interface query statement.
17. The method of claim 16, wherein the query optimization comprises a predicate push down technique.
18. The method as claimed in claim 15, wherein the mapping table query procedure further comprises:
connecting to the consumer electronic device by the coordination module using java database connection technology.
19. The method of claim 11, wherein the storage device stores a coordination module and an execution module, and wherein the method further comprises:
storing, by the execution module, the customer data in the storage device;
performing, by the execution module, a summary calculation on the customer data to obtain a summary result; and
transmitting, by the coordination module, the aggregated result to a consumer electronic device.
20. The method of claim 11, wherein the system is a federated query system.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210927641.6A CN115309986A (en) | 2022-08-03 | 2022-08-03 | System and method for mapping table of management interface |
TW111133513A TWI819773B (en) | 2022-08-03 | 2022-09-05 | System and method for managing mapping table of interface |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210927641.6A CN115309986A (en) | 2022-08-03 | 2022-08-03 | System and method for mapping table of management interface |
Publications (1)
Publication Number | Publication Date |
---|---|
CN115309986A true CN115309986A (en) | 2022-11-08 |
Family
ID=83859743
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210927641.6A Pending CN115309986A (en) | 2022-08-03 | 2022-08-03 | System and method for mapping table of management interface |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115309986A (en) |
TW (1) | TWI819773B (en) |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6151624A (en) * | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US20060004857A1 (en) * | 2004-07-01 | 2006-01-05 | International Business Machines Corporation | Method, system and program product for normalization of database result sets |
CN114116268A (en) * | 2021-11-02 | 2022-03-01 | 南京苏宁电子信息技术有限公司 | Method and device for checking Flink SQL statement, computer equipment and storage medium |
CN114416721A (en) * | 2021-12-14 | 2022-04-29 | 杭州安恒信息技术股份有限公司 | Automatic table building method, system, readable storage medium and computer equipment |
CN114625792A (en) * | 2022-02-24 | 2022-06-14 | 安翰科技(武汉)股份有限公司 | Method and device for exporting query result of database |
-
2022
- 2022-08-03 CN CN202210927641.6A patent/CN115309986A/en active Pending
- 2022-09-05 TW TW111133513A patent/TWI819773B/en active
Also Published As
Publication number | Publication date |
---|---|
TWI819773B (en) | 2023-10-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8321450B2 (en) | Standardized database connectivity support for an event processing server in an embedded context | |
CN111104421A (en) | Data query method and device based on data interface standard configuration | |
AU2017200895B2 (en) | Software integration testing with unstructured database | |
CN108647357B (en) | Data query method and device | |
US10353723B2 (en) | PL/SQL language parsing at a virtual machine | |
CN110222028B (en) | Data management method, device, equipment and storage medium | |
US11263542B2 (en) | Technologies for auto discover and connect to a rest interface | |
CN112579461A (en) | Assertion processing method, system and storage medium | |
CN111752916B (en) | Data acquisition method and device, computer readable storage medium and electronic equipment | |
CN112015766A (en) | Data processing method and device based on pipelining and data processing system | |
CN115309986A (en) | System and method for mapping table of management interface | |
US8825630B2 (en) | Method and system for generic enterprise search adapter queries | |
US20210263928A1 (en) | System and method of fetching data from an external program | |
CN114153438A (en) | API automatic generation system | |
CN114358596A (en) | Index calculation method and device | |
CN110309211B (en) | Method for positioning ETL process problem and related equipment | |
CN113448985A (en) | API (application program interface) interface generation method, calling method and device and electronic equipment | |
US8321844B2 (en) | Providing registration of a communication | |
CN116414846A (en) | Transaction processing method, device, equipment and storage medium based on database connection | |
TW202407556A (en) | System and method for managing mapping table of interface | |
CN116340336A (en) | Data query method and device based on database analysis engine | |
CN113190264B (en) | JPA-based automatic data version generation and application device and method | |
CN113704320B (en) | Data processing method, device, electronic equipment and storage medium | |
CN112650773A (en) | Data query method and device, electronic equipment and storage medium | |
CN116842078A (en) | Data access method, electronic device and computer readable storage medium |
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 |