CN112966004A - Data query method and device, electronic equipment and computer readable medium - Google Patents
Data query method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN112966004A CN112966004A CN202110238676.4A CN202110238676A CN112966004A CN 112966004 A CN112966004 A CN 112966004A CN 202110238676 A CN202110238676 A CN 202110238676A CN 112966004 A CN112966004 A CN 112966004A
- Authority
- CN
- China
- Prior art keywords
- data
- query
- data source
- physical
- physical table
- 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
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000004590 computer program Methods 0.000 claims description 13
- 238000013075 data extraction Methods 0.000 claims description 13
- 230000008569 process Effects 0.000 claims description 11
- 238000004364 calculation method Methods 0.000 claims description 8
- 238000000605 extraction Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 238000009795 derivation Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 230000008859 change Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000008447 perception Effects 0.000 description 3
- 238000012356 Product development Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012935 Averaging Methods 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 210000001520 comb Anatomy 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
- G06F16/24558—Binary matching operations
- G06F16/2456—Join operations
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a data query method and device, relates to the technical field of big data, and further relates to the technical field of data query. The specific implementation scheme is as follows: receiving a data query request; acquiring a corresponding relation between a logic table and a physical table of each data source based on a database connection pool connected with at least one data source; and determining a query result based on the query request and the corresponding relation, so that the embodiment saves the configuration cost of the database.
Description
Technical Field
The present application relates to the field of computer technologies, in particular to the field of big data technologies, and further relates to the field of data query technologies, and in particular, to a data query method, an apparatus, an electronic device, a computer-readable medium, and a computer program product.
Background
In a general standardized database product, the organization and structure of a data source are often fixed, but in an actual scene, a local data source of a client may need to be fused with a plurality of isomorphic or heterogeneous data sources, so that when the product is deployed privately, problems of nonstandard data design, unmatched organization and structure of a plurality of data sources, data stored in a plurality of heterogeneous data sources and the like may exist, so that data of the data sources cannot be accurately queried frequently, and the effectiveness of data query is reduced.
Disclosure of Invention
A data query method, an apparatus, an electronic device, a computer readable medium, and a computer program product are provided.
According to a first aspect, there is provided a data query method, the method comprising: receiving a data query request; acquiring a corresponding relation between a logic table and a physical table of each data source based on a database connection pool connected with at least one data source; and determining a query result based on the query request and the corresponding relation.
According to a second aspect, there is provided a data query apparatus, the apparatus comprising: a receiving unit configured to receive a data query request; an acquisition unit configured to acquire a correspondence relationship between the logical table and a physical table of each data source based on a database connection pool connected to at least one data source; a determination unit configured to determine a query result based on the query request and the correspondence.
According to a third aspect, there is provided an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.
According to a fourth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform a method as described in any one of the implementations of the first aspect.
According to a fifth aspect, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method as described in any of the implementations of the first aspect.
According to the data query method and the data query device provided by the embodiment of the application, firstly, a data query request is received; secondly, acquiring a corresponding relation between the logic table and a physical table of each data source based on a database connection pool connected with at least one data source; and finally, determining a query result based on the query request and the corresponding relation. Therefore, when the data source is deployed, only the mapping relation of the logical table and the physical table of the data source needs to be configured, and the condition of the real data source of a product does not need to be concerned in the data query process, the query of the logical table can be automatically converted into the query of the real data source without perception, so that the data source deployment cost is reduced, and the data query effectiveness and the data query efficiency are improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a flow diagram according to one embodiment of a data query method of the present application;
FIG. 2 is a flowchart of a method for obtaining correspondence between logical tables and physical tables of respective data sources according to the present application;
FIG. 3 is a flow chart of one method of determining query results according to the present application;
FIG. 4 is a schematic block diagram of an embodiment of a data query device according to the present application;
fig. 5 is a block diagram of an electronic device for implementing the data query method according to the embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Aiming at the problem that a plurality of data sources are not matched in organization and structure when a product is privatized to be deployed, a traditional solution mode generally combs out a data source meeting the data structure requirement of the privatized product through a data management team, or adjusts the data source based on the current data source situation to develop a customized product adaptive to the current data source situation, but the two modes need to spend large manpower and material resources to deploy the data source, and the development cost is high. The data query method and the data query device can shield the real data source situation of the product in the processes of design development and user data query, namely, a product development team can design the data structure of the logic table based on the current situation of the product during development without concerning the real data source situation; when a product development team deploys a product, only the mapping relation between the logic table and the physical table needs to be configured, so that a user can perform unaware query on the logic table, automatically convert the query into query on a real data source, execute the query and return corresponding data of the real data source.
In order to understand the technical solutions mentioned in the embodiments of the present application, several technical terms referred to in the present application are briefly described below.
Data Source (Data Source), which refers to a database or database server used by a database application. A data source is a device or raw media that provides some desired data. All information for establishing a database connection is stored in the data source. Just as files can be found in a file system by specifying the file name, the corresponding database connection can be found by providing the correct data source name.
A database connection pool responsible for allocating, managing and releasing database connections, which allows an application to reuse one existing database connection instead of reestablishing one; database connections with idle times exceeding the maximum idle time are released to avoid database connection misses caused by not releasing the database connections.
The physical table may be a table actually existing in the data source. The physical table is a table for storing entity data, also called physical fact table. "fact" refers to what actually exists in the business, such as the fact that the user is, and the fact that the user trades orders generated during the process. For example, in a physical fact table for user facts, each column contains information of each specific type for all users, such as numbers of all users, and each row contains information of a specific user, such as number of the user, location where the user appears, and time when the user appears.
A logical table, which may be understood as a view in a database, is a virtual table. The mapping table can be mapped to one physical table or can be composed of a plurality of physical tables, and the physical tables can be from different data sources. For example, for Mysql, Hbase, and ElasticSearch data sources, a logical table is constructed, requiring only fields that have the same meaning. This field is the primary Key in Mysql data source, the value for generating Rowkey in Hbase, and Key in ES.
FIG. 1 shows a process 100 according to an embodiment of a data query method of the present application, the data query method comprising the steps of:
In this embodiment, the query request may be a request sent by a user or a developer, where the query request includes query information, and the query information may include: inquiring a logic table, inquiring fields and operating types; the query logical table is a logical table that a user or a developer needs to query, the query field is a field of the logical table that needs to query, and the operation type is an operation performed on data in the physical table, such as query, deletion, writing and the like. Optionally, when there are a plurality of logical tables or query fields, the query information may further include: and inquiring rules and association relations. The query rule is a rule used for querying a plurality of logic tables or a plurality of query fields, and for example, the query rule includes: sorting, aggregation mode (summation, averaging) of aggregation fields and aggregation fields, query filtering, number of returned query results, and the like. The association relationship in the query information may be a correspondence relationship between the logic table and the query field, or an association relationship between a plurality of logic tables, or an association relationship between a plurality of query fields, and the logic calculation expression of the query information may be obtained based on the query rule and the association relationship.
It should be noted that, for query requests issued by different people, the presentation forms of the query results fed back are different. For example, for a query request issued by a user, the query results are represented using fields of a logical table that can be understood by the user. For the query request sent by the developer, the query result can be directly expressed by using the field of the physical table of the data source, and can also be expressed by using the field of the converted logical table.
And 102, acquiring a corresponding relation between the logic table and the physical table of each data source based on a database connection pool connected with at least one data source.
In this embodiment, the execution subject on which the data query method operates may create a database connection pool connected to at least one data source, and may also be configured to receive a data query request.
In this embodiment, the at least one data source is a data source corresponding to a product, and all data sources in the at least one data source may be homogeneous data sources, for example, all data sources are Mysql data sources; the at least one data source may also be a heterogeneous data source, for example, the at least one data source may include Mysql, Oracle, SqlServer, PostgreSql, ElasticSearch, Doris, and the like type data sources; the at least one data source may be a data source consisting of a plurality of homogeneous data sources and a plurality of heterogeneous data sources.
In this embodiment, the correspondence between the logical table and the physical table of each data source is obtained after the database connection pool is created.
In this embodiment, after the creation of the database connection pool is completed, the configuration information of the logic table may be extracted first, and then, the corresponding relationship between the logic table and the physical tables of the data sources may be obtained according to the configuration information of the logic table.
In this embodiment, the configuration information of the logical table may be extracted by scanning the entity class code. The entity class code is mainly used as a class existing on a data management and service logic processing level; the main responsibility of the entity class code to distinguish entity classes during the analysis phase is to store and manage information within the system, and the entity class code may also have behaviors that are closely related to the entity object it represents. In this embodiment, obtaining the configuration information of the logic table by scanning the entity class code includes: and directly scanning codes related to the logic table in the entity class codes or configuring the entity class codes to obtain all configuration contents related to the logic table.
In this embodiment, the logical table may be a table obtained by associating a plurality of lower physical fact tables with the primary key, and the logical table is different from the physical table, and does not generate an actual physical table, but records a correspondence relationship with a physical table of each data source in the metadata.
The configuration information of the logic table is obtained by scanning all the information related to the logic table in the entity class code. After obtaining the configuration information of the logic table, the configuration information of the logic table may be loaded to the memory, and further, when receiving the query request, the corresponding relationship between the logic table and the physical tables of the data sources is extracted from the configuration information of the logic table.
The configuration information of the logical table may include creation information and association information of the logical table. The above creation information includes a table name of the logical table, a column name (field name) of each column of the logical table, and the like. The association information includes association between the logical table and the corresponding column of the physical table of each data source.
The correspondence between the logical table and the physical tables of the data sources may include a correspondence between a table name of the logical table and a physical table of each data source, for example, logical table 1 corresponds to physical table 1 and physical table 2. The correspondence between the logical table and the physical table of each data source may further include: and the association relationship between the logic table and the corresponding column of the physical table of each data source.
In this embodiment, the query request includes query information, the query information includes a query logic table (table name), a query field, and the like, and the query logic table belongs to a logic table. The method comprises the steps of determining a physical table of a data source corresponding to a query logical table based on corresponding relations between the logical table and the physical tables of the data sources, further determining contents of fields of the physical tables of the data sources corresponding to the query logical table based on query fields, and obtaining the contents of the fields of the physical tables of the data sources through query statements corresponding to the data sources, namely query results of query information in query requests.
In this embodiment, at least one data source may include multiple heterogeneous data sources, and therefore, the query result may be data obtained from the multiple heterogeneous data sources, and an execution subject on which the data query method is executed supports the standard SQL syntax, and adds a new syntax to the standard SQL syntax to support a specific query statement of a part of the heterogeneous data sources, such as the match syntax of the ElasticSearch data source. After receiving the query information, the execution subject intercepts and parses the rewritten SQL statement, converts the rewritten SQL statement into a real query corresponding to the data source, and executes the statement query.
For the convenience of understanding of users or developers, the query result can be directly expressed by using the fields of the physical table of the data source, and also can be expressed by using the fields of the converted logical table.
The data query method provided by the embodiment of the application comprises the steps of firstly, receiving a data query request; secondly, acquiring a corresponding relation between the logic table and a physical table of each data source based on a database connection pool connected with at least one data source; and finally, determining a query result based on the query request and the corresponding relation. Therefore, when the data source is deployed, only the mapping relation of the logical table and the physical table of the data source needs to be configured, and the condition of the real data source of a product does not need to be concerned in the data query process, the query of the logical table can be automatically converted into the query of the real data source without perception, so that the data source deployment cost is reduced, and the data query effectiveness and the data query efficiency are improved.
In some optional implementations of this embodiment, the creating process of the database connection pool includes: acquiring configuration information of at least one data source; a database connection pool is created based on the configuration information of all data sources.
In this alternative implementation, the database connection pool may be created based on configuration information of the data sources. The configuration information of the data source includes: connection information and metadata of the data source. The connection information is connection information of the data source, the connection information is necessary information that the database connection driver can be connected to the data source, and the connection information may include a name and a password of the data source. Metadata of a data source is data in at least one data source that describes the data of the data source and the environment in which the data source is located.
The configuration information of the data source may be obtained by scanning a configuration file of the data source, and the configuration file may be a file provided by a supplier of the data source or a file developed by a developer about the data source.
In the optional implementation manner, after the configuration information of at least one data source is acquired, the database connection pool is created based on the configuration information of all the data sources, and the implementation is simple and convenient.
Optionally, after determining the configuration information of the data sources, it may also be detected whether the configuration information of each data source is correct, and when all the configuration information is correct, a database connection pool is created based on the configuration information of all the data sources. Wherein detecting whether the configuration information of each data source is correct may include: and establishing data source connection, sending a data packet to the data source, and further determining whether the configuration information of other data sources is correct or not if the data packet is successfully sent until the configuration information of all the data sources is correct.
Optionally, after the database connection pool is created, a data packet may be sent to each data source, and whether the connection of each data source is normal is further verified through whether the data packet is successfully sent.
In the optional implementation mode, a database connection pool is created based on the configuration information of at least one data source, and reliable database connection is provided for isomorphic or heterogeneous data sources; in the process of creating the database connection pool, whether the configuration information of all the data sources is correct or not is detected, and the reliability of the data sources in database connection is improved.
FIG. 2 illustrates a flow 200 of a method of obtaining correspondence between logical tables and physical tables of various data sources. The method for acquiring the corresponding relation between the logical table and the physical tables of the data sources comprises the following steps:
In this alternative implementation, all entity class codes with logical table annotations are scanned, that is, entities related to the logical table in the entity class codes are scanned. See the following configuration examples:
@Data
@LogicTable(tables＝“datasource1.action”)
public class ContractDemo{
@Column(name＝“id”，type＝“int”,primaryKey＝true)
public Integer id；
@Column(name＝“action_name”，type＝“varchar”)
public String name；
in this example, conteractdemo is the name of a logical table, and the datasource1.action is a physical table corresponding to the logical table. The relevant contents in @ Column are all relevant fields related to the physical table.
Based on the configuration example, all entities with @ LogicTable annotation can be scanned, the annotation information on the field is checked and loaded and configured into the memory, so that the configuration of a physical table of a single or multiple data sources for one logical table is supported. In this optional implementation, the configuration information of the logic table related to the logic table can be conveniently and quickly obtained by scanning all entity class codes with the logic table annotation.
In this optional implementation, one logical table may correspond to multiple physical tables of multiple data sources, and based on the configuration information of the logical table, all the physical tables corresponding to the logical table and the fields of the physical tables of all the data sources corresponding to the fields of the logical table may be obtained.
For example, in an actual scenario, a travel track of a user needs to be acquired to determine the health code status of the user. Wherein the fields of physical table 1 of the first data source include: user ID, user presence location, and user presence time. The fields of physical table 2 of the second data source include: venue ID, venue name, venue location, venue risk level. The first data source and the second data source may be homogeneous data sources or heterogeneous data sources. The fields of the logical table of the product include: the user ID, the place where the user appears, whether the user is in a medium-high risk area or not can be obtained through the configuration information of the logic table, and the corresponding relation between the logic table and the fields of the physical tables of all the data sources is configured as follows:
the logic table- > user ID corresponds to the physical table 1- > user ID;
the logic table- > the user appearance place corresponds to the physical table 1- > the user appearance place;
logical table- > whether the region with medium and high risk corresponds to the physical table 2- > site risk level.
According to the method for obtaining the corresponding relationship between the logical table and the physical tables of the data sources, after the creation of the database connection pool connected with at least one data source is completed, all entity class codes with logical table annotations are scanned to obtain the configuration information of the logical table, and the corresponding relationship between the logical table and the physical tables of the data sources is obtained based on the configuration information.
In some optional implementation manners of this embodiment, the correspondence between the logical table and the physical table of each data source may also be a relationship obtained by pre-extraction, and specifically, the method for obtaining the correspondence between the logical table and the physical table of each data source may further include: scanning all entity class codes with logic table annotations to obtain configuration information of the logic table; and obtaining the corresponding relation between the logic table and the physical tables of the data sources based on the configuration information of the logic table. Storing the corresponding relation between the logic table and the physical tables of the data sources in a memory; and in response to the fact that the field of the at least one physical table or the configuration information of the at least one data source is changed, updating the corresponding relation between the logic table and the physical table of each data source based on the changed field of the at least one physical table or the configuration information of the at least one data source.
In this optional implementation, whether a field of a physical table in a correspondence between configuration information or a logical table of at least one data source and a physical table of each data source changes may be checked at regular time; and updating the corresponding relation between the logic table and the physical table of each data source based on the change of the field of the at least one physical table or the configuration information of the at least one data source.
In this optional implementation manner, when it is checked that a field of a physical table or at least one data source configuration information in a correspondence between a logical table and physical tables of each data source changes, it indicates that one or more of a connection pool of a database of a current product, a physical table of a data source, or a correspondence between a logical table and a physical table may have a substantial change, and therefore, it is necessary to update the correspondence between the logical table and the physical tables of each data source, in this embodiment, updating the correspondence between the logical table and the physical tables of each data source includes: and retrieving the configuration information of the logic table, and retrieving the corresponding relation between the logic table and the physical tables of the data sources.
In this optional implementation manner, the execution body on which the data query method runs is further provided with a configuration center, and a user or a developer may set a time interval for timing check in the configuration center (the time interval may be set according to a system setting requirement, for example, the time interval is 1s), so as to achieve a purpose of timing check on a change of the configuration information or the logical table of at least one data source and the physical table of each data source.
In the optional implementation manner, whether the physical table of the data source or the configuration information of the data source is changed or not is checked at regular time, so that the corresponding relationship between the logic table and the physical table can be re-extracted along with the change of the configuration information of the data source or the physical table of the data source, the unavailability of service caused by the change of the physical table of the data source is avoided, and the reliability of data query is improved.
FIG. 3 shows a flow 300 of a method of determining query results. The method for determining the query result comprises the following steps:
In this optional implementation manner, the correspondence relationship refers to a correspondence relationship between the logical table and the physical tables of each data source, and since the configuration information of the logical table includes the physical tables of the data sources corresponding to all the logical tables, the physical tables corresponding to all the logical tables and the association relationship between all the logical tables and each physical table can be determined based on the correspondence relationship between the logical table and each physical table of each data source. Associations represent structural relationships between objects of different classes, and associations between physical and logical tables may connect fields of multiple classes together over a period of time.
Further, the physical tables related to the query information in the query request can be selected from the physical tables corresponding to all the logical tables, and the relationship between the physical table and the logical table can be selected from the association relationship between all the logical tables and each physical table. It should be noted that the physical table related to the query information may be at least one physical table in one data source, or may be at least one physical table in a plurality of homogeneous or heterogeneous data sources.
In this optional implementation manner, the physical table corresponding to the query information in the query request may be a target query physical table from which the query result can be directly extracted, after the physical table corresponding to the query information is determined, the type of the data source of the physical table is determined, based on the association relationship between the physical table and the logical table, a query statement corresponding to the type of the data source of the physical table is generated according to the query information, and the data source corresponding to the physical table is queried based on the query statement, so as to obtain the query result.
When the physical table corresponding to the query information is not a target query physical table from which the query result can be directly extracted, the target query physical table needs to be obtained first, and in some optional implementation manners of this embodiment, determining the query result according to an association relationship between the physical table, and the logical table corresponding to the query request includes: generating a target query physical table according to the physical table corresponding to the query request; generating a data extraction statement of a data source corresponding to the target query physical table according to the logic calculation expression of the query request; extracting corresponding data from the target query physical table based on the data extraction statement; and obtaining a query result according to the corresponding data.
In the optional implementation mode, the target query physical table is generated firstly, the data extraction statement corresponding to the target query physical table is generated based on the logic calculation expression of the query information, and the query result corresponding to the query information is obtained by adopting the data extraction statement, so that the automatic query of the data at the bottom layer of the data source is realized, the database type of the data source does not need to be concerned, and the user query experience is improved.
Optionally, the method for determining a query result may further include: according to the association relation among the physical table, the physical table and the logical table corresponding to the query request, a corresponding query plan can be generated, and the query plan comprises: querying a target physical table, querying a physical field, filtering a condition, and executing a pre-dependency. And analyzing and generating a real query statement for the data source according to the query plan and the data source type corresponding to the query target physical table. In the process of executing the real query statement, the parallel execution and the pre-dependent query path can be determined according to the query plan, and the multi-path query is executed in parallel, so that the query performance is maximally improved. The result sets obtained by the multiple queries are merged and sorted to obtain query results, and it should be noted that the query request includes query information, and the query information includes: the operation type can use a distributed lock to ensure the consistency of modification operation when the operation type comprises data writing or deleting and the query field of the query information relates to a plurality of physical tables; the module will add distributed row locks based on the modified target data source and target data rows to ensure minimum lock granularity.
When the query request is sent by the user, the field name can be transcribed to ensure that the field name is consistent with the field of the logic table in order to facilitate the user to intuitively know the query result.
In some optional implementations of this embodiment, obtaining the query result according to the corresponding data includes: based on the corresponding relation, converting the corresponding data extracted from the target query physical table into data of a field corresponding to the logical table; and taking the data of the corresponding field of the logical table as a query result.
In the optional implementation mode, the query of the user for the query information is based on the data of the logical table of the product status, after the data is extracted from the target query physical table, the data is converted into the data of the corresponding field of the logical table, and the corresponding field of the logical table and the data corresponding to the field are output to the user, so that the user can know the content of the data more visually and vividly, the user does not need to know the configuration of the field of the physical table of the data source, and the user experience is improved.
According to the method for determining the query result, based on the query request and the corresponding relationship between the logical table and the physical table of each data source, the physical table corresponding to the query request, the association relationship between the physical table and the logical table are determined, and the query result is determined according to the association relationship between the physical table and the logical table.
With further reference to fig. 4, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a data query apparatus, which corresponds to the embodiment of the method shown in fig. 1, and which is particularly applicable to various electronic devices.
As shown in fig. 4, the data query apparatus 400 provided in this embodiment includes: receiving section 401, acquiring section 402, and determining section 403. The receiving unit 401 may be configured to receive a data query request. The obtaining unit 402 may be configured to obtain a correspondence between the logical table and the physical table of each data source based on a database connection pool connected to at least one data source. The determining unit 403 may be configured to determine a query result based on the query request and the corresponding relationship.
In the present embodiment, in the data query apparatus 400: the specific processing and the technical effects of the receiving unit 401, the obtaining unit 402, and the determining unit 403 can refer to the related descriptions of step 101, step 102, and step 103 in the corresponding embodiment of fig. 1, which are not described herein again.
In some optional implementations of this embodiment, the database connection pool in the receiving unit 401 is created by the following modules: an acquisition module (not shown), a creation module (not shown). The obtaining module may be configured to obtain configuration information of at least one data source. The creation module may be configured to create a database connection pool based on the configuration information of all data sources.
In some optional implementation manners of this embodiment, the obtaining unit 402 includes: a scanning module (not shown), a relationship obtaining module (not shown). The scanning module may be configured to scan all entity class codes with the logic table annotation to obtain configuration information of the logic table. The relationship obtaining module may be configured to obtain a corresponding relationship between the logical table and the physical table of each data source based on the configuration information of the logical table.
In some optional implementation manners of this embodiment, the obtaining unit 402 further includes: a memory module (not shown), a configuration module (not shown). The storage module may be configured to store the correspondence between the logical table and the physical table of each data source in a memory. The configuration module may be configured to, in response to determining that the field of the at least one physical table or the configuration information of the at least one data source changes, update the corresponding relationship between the logical table and the physical table of each data source based on the changed field of the at least one physical table or the configuration information of the at least one data source.
In some optional implementations of this embodiment, the determining unit 403 includes: a relationship determination subunit (not shown in the figure), and a result determination subunit (not shown in the figure). The relationship determination subunit may be configured to determine, based on the query request and the correspondence, an association relationship between the physical table, and the logical table corresponding to the query request. The result determination subunit may be configured to determine the query result according to an association relationship among the physical table, and the logical table corresponding to the query request.
In some optional implementations of this embodiment, the result determining subunit includes: a table generating module (not shown), a sentence generating module (not shown), an extracting module (not shown), and a result obtaining module (not shown). The table generating module may be configured to generate a target query physical table according to a physical table corresponding to the query request. The statement generation module may be configured to generate a data extraction statement of a data source corresponding to the target query physical table according to the logical calculation expression of the query request. The extraction module may be configured to extract corresponding data from the target lookup physical table based on the data extraction statement. The result obtaining module may be configured to obtain the query result according to the corresponding data.
In some optional implementations of this embodiment, the result obtaining module includes: a data extraction sub-module (not shown), resulting in a sub-module (not shown). The data extraction sub-module may be configured to convert, based on the correspondence, corresponding data extracted from the target query physical table into data of a field corresponding to the logical table. The result obtaining submodule can be configured to use the data of the corresponding field of the logical table as a query result.
In the data query apparatus provided in the embodiment of the present application, first, the receiving unit 401 receives a data query request; secondly, the obtaining unit 402 obtains a corresponding relationship between the logical table and the physical table of each data source based on the database connection pool connected to at least one data source; finally, the determination unit 403 determines a query result based on the query request and the correspondence relationship. Therefore, when the data source is deployed, only the mapping relation of the logical table and the physical table of the data source needs to be configured, and the condition of the real data source of a product does not need to be concerned in the data query process, the query of the logical table can be automatically converted into the query of the real data source without perception, so that the data source deployment cost is reduced, and the data query effectiveness and the data query efficiency are improved.
There is also provided, in accordance with an embodiment of the present application, an electronic device, a readable storage medium, and a computer program product.
FIG. 5 illustrates a schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 5, the apparatus 500 comprises a computing unit 501 which may perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)502 or a computer program loaded from a storage unit 508 into a Random Access Memory (RAM) 503. In the RAM503, various programs and data required for the operation of the device 500 can also be stored. The calculation unit 501, the ROM 502, and the RAM503 are connected to each other by a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
A number of components in the device 500 are connected to the I/O interface 505, including: an input unit 506 such as a keyboard, a mouse, or the like; an output unit 507 such as various types of displays, speakers, and the like; a storage unit 508, such as a magnetic disk, optical disk, or the like; and a communication unit 509 such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The computing unit 501 may be a variety of general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 501 executes the respective methods and processes described above, such as the data query method. For example, in some embodiments, the data query method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM 502 and/or the communication unit 509. When the computer program is loaded into the RAM503 and executed by the computing unit 501, one or more steps of the data query method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the data query method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present application may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, and the present invention is not limited herein.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (17)
1.A method of data query, the method comprising:
receiving a data query request;
acquiring a corresponding relation between a logic table and a physical table of each data source based on a database connection pool connected with at least one data source;
and determining a query result based on the query request and the corresponding relation.
2. The method of claim 1, wherein the database connection pool creation process comprises:
acquiring configuration information of at least one data source;
a database connection pool is created based on the configuration information of all data sources.
3. The method according to claim 1 or 2, wherein the obtaining the correspondence between the logical table and the physical table of each data source based on the database connection pool connected to at least one data source comprises:
scanning all entity class codes with logic table annotations to obtain configuration information of the logic table;
and obtaining the corresponding relation between the logic table and the physical tables of the data sources based on the configuration information of the logic table.
4. The method of claim 3, wherein the obtaining a correspondence between the logical table and the physical table of each data source based on the database connection pool connected to the at least one data source further comprises:
storing the corresponding relation between the logic table and the physical tables of the data sources in a memory;
and in response to the fact that the field of the at least one physical table or the configuration information of the at least one data source is changed, updating the corresponding relation between the logic table and the physical table of each data source based on the changed field of the at least one physical table or the configuration information of the at least one data source.
5. The method of claim 1 or 2, wherein said determining a query result based on the query request and the correspondence comprises:
determining an association relation among a physical table, the physical table and the logic table corresponding to the query request based on the query request and the corresponding relation;
and determining a query result according to the physical table corresponding to the query request, the association relationship between the physical table and the logic table.
6. The method of claim 5, wherein the determining a query result according to the association relationship among the physical table, the physical table and the logical table corresponding to the query request comprises:
generating a target query physical table according to the physical table corresponding to the query request;
generating a data extraction statement of a data source corresponding to the target query physical table according to the logic calculation expression of the query request;
extracting corresponding data from the target query physical table based on the data extraction statement;
and obtaining a query result according to the corresponding data.
7. The method of claim 6, wherein said deriving a query result from said corresponding data comprises:
based on the corresponding relation, converting the corresponding data extracted from the target query physical table into data of a field corresponding to a logical table;
and taking the data of the corresponding field of the logic table as a query result.
8. A data query device, the device comprising:
a receiving unit which receives a data query request;
an acquisition unit configured to acquire a correspondence relationship between the logical table and a physical table of each data source based on a database connection pool connected to at least one data source;
a determination unit configured to determine a query result based on the query request and the correspondence.
9. The apparatus of claim 8, wherein the database connection pool in the receiving unit is created by:
an acquisition module configured to acquire configuration information of at least one data source;
a creation module configured to create a database connection pool based on the configuration information of all data sources.
10. The apparatus according to claim 8 or 9, wherein the obtaining unit comprises:
the scanning module is configured to scan all entity class codes with the logic table annotation to obtain configuration information of the logic table;
and the relation obtaining module is configured to obtain the corresponding relation between the logic table and the physical table of each data source based on the configuration information of the logic table.
11. The apparatus of claim 10, wherein the obtaining unit further comprises:
the storage module is configured to store the corresponding relation between the logic table and the physical table of each data source in a memory;
and the configuration module is configured to respond to the determination that the field of the at least one physical table or the configuration information of the at least one data source changes, and update the corresponding relation between the logical table and the physical table of each data source based on the changed field of the at least one physical table or the configuration information of the at least one data source.
12. The apparatus of claim 8 or 9, wherein the determining unit comprises:
a relationship determination subunit configured to determine, based on the query request and the correspondence, an association relationship between a physical table corresponding to the query request, the physical table, and the logical table;
and the result determining subunit is configured to determine a query result according to the association relation among the physical table, the physical table and the logic table corresponding to the query request.
13. The apparatus of claim 12, wherein the result determination subunit comprises:
the table generation module is configured to generate a target query physical table according to the physical table corresponding to the query request;
a statement generation module configured to generate a data extraction statement of a data source corresponding to the target query physical table according to the logical calculation expression of the query request;
an extraction module configured to extract corresponding data from the target query physical table based on the data extraction statement;
and the result obtaining module is configured to obtain a query result according to the corresponding data.
14. The apparatus of claim 13, wherein the result derivation module comprises:
a data extraction sub-module configured to convert the corresponding data extracted from the target query physical table into data of a field corresponding to a logical table based on the correspondence;
and the result obtaining submodule is configured to take the data of the corresponding field of the logic table as a query result.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.
17. A computer program product comprising a computer program which, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110238676.4A CN112966004B (en) | 2021-03-04 | 2021-03-04 | Data query method, device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110238676.4A CN112966004B (en) | 2021-03-04 | 2021-03-04 | Data query method, device, electronic equipment and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112966004A true CN112966004A (en) | 2021-06-15 |
| CN112966004B CN112966004B (en) | 2023-07-28 |
Family
ID=76276570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110238676.4A Active CN112966004B (en) | 2021-03-04 | 2021-03-04 | Data query method, device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112966004B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434572A (en) * | 2021-06-24 | 2021-09-24 | 中国工商银行股份有限公司 | Data query method, query system, device, storage medium and program product |
| CN113761024A (en) * | 2021-08-27 | 2021-12-07 | 德邦证券股份有限公司 | Real-time query method and system of distributed SQL |
| CN114154026A (en) * | 2021-11-12 | 2022-03-08 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114610719A (en) * | 2022-03-15 | 2022-06-10 | 云粒智慧科技有限公司 | Cross-cluster data processing method and device, electronic equipment and storage medium |
| CN116383238A (en) * | 2023-06-06 | 2023-07-04 | 湖南红普创新科技发展有限公司 | Data virtualization system, method, device, equipment and medium based on graph structure |
| CN116561132A (en) * | 2023-07-06 | 2023-08-08 | 深圳市明源云科技有限公司 | Service data query method, electronic device and readable storage medium |
| WO2024092926A1 (en) * | 2022-10-31 | 2024-05-10 | 蚂蚁区块链科技(上海)有限公司 | Method and device for generating data table |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790322A (en) * | 2004-12-17 | 2006-06-21 | 国际商业机器公司 | Method and system of creating a logical table from multiple differently formatted physical tables |
| US20060190434A1 (en) * | 2005-02-24 | 2006-08-24 | International Business Machines Corporation | Query rebinding for high-availability database systems |
| US20100094902A1 (en) * | 2008-10-09 | 2010-04-15 | International Business Machines Corporation | Automated data source assurance in distributed databases |
| CN107491510A (en) * | 2017-08-03 | 2017-12-19 | 国网江苏省电力公司信息通信分公司 | One kind mixing heterogeneous data source unified query system and distributed enquiring method |
| CN108108456A (en) * | 2017-12-28 | 2018-06-01 | 重庆邮电大学 | A kind of information resources distributed enquiring method based on metadata |
| CN108628986A (en) * | 2018-04-27 | 2018-10-09 | 深圳市牛鼎丰科技有限公司 | Data query method, apparatus, computer equipment and storage medium |
| CN110674228A (en) * | 2019-09-23 | 2020-01-10 | 阿里巴巴集团控股有限公司 | Data warehouse model construction and data query method, device and equipment |
-
2021
- 2021-03-04 CN CN202110238676.4A patent/CN112966004B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790322A (en) * | 2004-12-17 | 2006-06-21 | 国际商业机器公司 | Method and system of creating a logical table from multiple differently formatted physical tables |
| US20060190434A1 (en) * | 2005-02-24 | 2006-08-24 | International Business Machines Corporation | Query rebinding for high-availability database systems |
| US20100094902A1 (en) * | 2008-10-09 | 2010-04-15 | International Business Machines Corporation | Automated data source assurance in distributed databases |
| CN107491510A (en) * | 2017-08-03 | 2017-12-19 | 国网江苏省电力公司信息通信分公司 | One kind mixing heterogeneous data source unified query system and distributed enquiring method |
| CN108108456A (en) * | 2017-12-28 | 2018-06-01 | 重庆邮电大学 | A kind of information resources distributed enquiring method based on metadata |
| CN108628986A (en) * | 2018-04-27 | 2018-10-09 | 深圳市牛鼎丰科技有限公司 | Data query method, apparatus, computer equipment and storage medium |
| CN110674228A (en) * | 2019-09-23 | 2020-01-10 | 阿里巴巴集团控股有限公司 | Data warehouse model construction and data query method, device and equipment |
Non-Patent Citations (1)
| Title |
|---|
| 曾艳梅;成长生;陆忠良;苏厚勤;: "一种基于元数据静动态数据联合查询方法的研究与实现", 计算机应用与软件, no. 01 * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434572A (en) * | 2021-06-24 | 2021-09-24 | 中国工商银行股份有限公司 | Data query method, query system, device, storage medium and program product |
| CN113761024A (en) * | 2021-08-27 | 2021-12-07 | 德邦证券股份有限公司 | Real-time query method and system of distributed SQL |
| CN113761024B (en) * | 2021-08-27 | 2023-12-08 | 德邦证券股份有限公司 | Real-time query method and system of distributed SQL |
| CN114154026A (en) * | 2021-11-12 | 2022-03-08 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114154026B (en) * | 2021-11-12 | 2024-07-02 | 北京达佳互联信息技术有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN114610719A (en) * | 2022-03-15 | 2022-06-10 | 云粒智慧科技有限公司 | Cross-cluster data processing method and device, electronic equipment and storage medium |
| WO2024092926A1 (en) * | 2022-10-31 | 2024-05-10 | 蚂蚁区块链科技(上海)有限公司 | Method and device for generating data table |
| CN116383238A (en) * | 2023-06-06 | 2023-07-04 | 湖南红普创新科技发展有限公司 | Data virtualization system, method, device, equipment and medium based on graph structure |
| CN116383238B (en) * | 2023-06-06 | 2023-08-29 | 湖南红普创新科技发展有限公司 | Data virtualization system, method, device, equipment and medium based on graph structure |
| CN116561132A (en) * | 2023-07-06 | 2023-08-08 | 深圳市明源云科技有限公司 | Service data query method, electronic device and readable storage medium |
| CN116561132B (en) * | 2023-07-06 | 2023-12-22 | 深圳市明源云科技有限公司 | Service data query method, electronic device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112966004B (en) | 2023-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112966004B (en) | Data query method, device, electronic equipment and computer readable medium | |
| US9305109B2 (en) | Method and system of adapting a data model to a user interface component | |
| US20170068409A1 (en) | Computer implemented system and method for dynamically modeling relationships between entities | |
| CN107665228A (en) | A kind of related information querying method, terminal and equipment | |
| US20150317331A1 (en) | Unified platform for application development | |
| US8677376B2 (en) | Expressing equivalency relationships with identity graphs across multiple environments to create change list to be traversed to conform the environments | |
| US20190303506A1 (en) | Adaptable adjacency structure for querying graph data | |
| CN110941629B (en) | Metadata processing method, apparatus, device and computer readable storage medium | |
| US20110252049A1 (en) | Function execution using sql | |
| US11442930B2 (en) | Method, apparatus, device and storage medium for data aggregation | |
| US11687568B2 (en) | Data catalog system for generating synthetic datasets | |
| CN114281803A (en) | Data migration method, device, equipment, medium and program product | |
| US9280361B2 (en) | Methods and systems for a real time transformation of declarative model and layout into interactive, digital, multi device forms | |
| CN117170655A (en) | Metadata processing method and device, data processing equipment and storage medium | |
| CN115408546A (en) | Time sequence data management method, device, equipment and storage medium | |
| EP3062245A1 (en) | Dynamic modular ontology | |
| US9026561B2 (en) | Automated report of broken relationships between tables | |
| US9201937B2 (en) | Rapid provisioning of information for business analytics | |
| CN114168119B (en) | Code file editing method, device, electronic equipment and storage medium | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN114153438A (en) | API automatic generation system | |
| CN116450682B (en) | Model generation method, device, equipment and medium based on data combination | |
| CN115052035B (en) | Message pushing method, device and storage medium | |
| US11704094B2 (en) | Data integrity analysis tool | |
| CN115458103B (en) | Medical data processing method, medical data processing device, electronic equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |