CN114896286A - Data resource query method and device - Google Patents

Abstract

The application provides a method and a device for querying data resources, which are applied to a service system, wherein the method comprises the following steps: responding to a query request aiming at a target data resource by a query party, and determining a target data resource entity corresponding to the target data resource; determining a target physical data table corresponding to the target data resource entity according to a mapping relation between the stored data resource entity and a physical data table in a data source; and acquiring the target data resource recorded in the target physical data table, and returning the target data resource to the inquiring party.

Description

Data resource query method and device

technical field

The present application relates to the field of data resource query, and in particular, to a data resource query method, apparatus, device, and computer-readable storage medium.

Background technique

Data resources refer to the data itself, that is, various data records accumulated in the operation of the enterprise, such as customer records, sales records, personnel records, purchasing records, financial data and inventory data. Through the connection between the business system and the data source, users can access the data resources stored in the data source based on the business system.

In the related art, data resources may come from different data sources, or the originally used data sources may also be changed, so for each data source, the business system needs to re-develop the business code used to complete the connection.

SUMMARY OF THE INVENTION

In order to overcome the problems existing in the related art, the present application provides a data resource query method, apparatus, device and computer-readable storage medium, which can solve the above problems.

According to a first aspect of the embodiments of the present application, a data resource query method is provided, the method comprising:

In response to a query request for a target data resource by a query party, determining a target data resource entity corresponding to the target data resource;

According to the mapping relationship between the stored data resource entity and the physical data table in the data source, determine the target physical data table corresponding to the target data resource entity;

Acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party.

According to a second aspect of the embodiments of the present application, a data resource query device is provided, including:

a query unit, configured to determine a target data resource entity corresponding to the target data resource in response to a query request by a query party for the target data resource;

a mapping unit, configured to determine a target physical data table corresponding to the target data resource entity according to the mapping relationship between the stored data resource entity and the physical data table in the data source;

The returning unit is configured to acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party.

According to a third aspect of the embodiments of the present application, an electronic device is provided, including: a processor and a memory;

the memory for storing computer programs;

The processor is configured to execute the data resource query method according to the first aspect by invoking the computer program.

According to a fourth aspect of the embodiments of the present application, there is provided a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the data resource query method described in the first aspect.

The technical solutions provided by the embodiments of the present application may include the following beneficial effects:

In the embodiment of the present application, by establishing a data resource entity, a mapping relationship is established between the data resource entity and the physical data table in the database, and it is ensured that the business code in the business system is used for docking access to the data resource entity , so that even if the physical data table corresponding to the data resource entity changes due to the change of the data source, it will not affect the docking access between the business code and the data resource entity in the business system, and only the mapping relationship corresponding to the data resource entity needs to be updated, and the If the original physical data table is changed to the changed physical data table, the access to the changed physical data table can be successfully completed without modifying the business code of the business system, which greatly reduces the impact of data source changes. extra workload.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not limiting of the present application.

Description of drawings

The accompanying drawings, which are incorporated into the specification and constitute a part of this application, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

FIG. 1 is a schematic structural diagram of a data resource system according to an exemplary embodiment of the present application.

FIG. 2 is a flowchart of a data resource query method according to an exemplary embodiment of the present application.

FIG. 3 is a multi-party interaction diagram of a data resource query method according to an exemplary embodiment of the present application.

FIG. 4 is a schematic structural diagram of an electronic device where a data query apparatus is located according to an exemplary embodiment of the present application.

Fig. 5 is a block diagram of a data query apparatus according to an exemplary embodiment of the present application.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as recited in the appended claims.

The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to limit the application. As used in this application and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited by these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information without departing from the scope of the present application. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determining."

Next, the embodiments of the present application will be described in detail.

FIG. 1 is a network architecture diagram of a data resource query system according to an exemplary embodiment of the present application. As shown in FIG. 1 , the data resource query system of the present application may include user-side devices 11-12, a service system 13, data sources 14-16, and the like.

The user-side devices 11-12 may be mobile phones, desktop computers, tablet devices, notebook computers or PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, VR glasses, etc.), which are not limited in this application. Based on the technical architecture adopted between the user-side equipment 11-12 and the service system 13, there will be certain differences. For example, when the user-side equipment 11-12 is based on the C/S architecture, the user-side equipment 11-12 can be installed and run on the service system 13 corresponding to The client (such as the client of the business application running on the business system 13), when based on the B/S architecture, a browser is installed and running on the user-side equipment 11-12; correspondingly, the user can use the user-side equipment The above-mentioned client or browser running on 11-12 realizes data interaction with the business system 13 . Specifically, when the user acts as the inquiring party, the user-side devices 11-12 can send a query request to the business system 13 according to the user operation, and provide the target data resources returned by the business system 13 to the user, such as displaying on the user-side device 11 -12 on the display.

The service system 13 may be an independent host or host cluster, or may be a virtual server carried by the above-mentioned independent host or host cluster. The service system 13 may run a service end of a service application for performing data interaction with the above-mentioned user-side devices 11-12 and data sources 14-16. Specifically, the service system 13 may query the target data resources maintained by the data sources 14-16 according to the query requests sent by the user-side devices 11-12, and provide the target data resources returned by the data sources 14-16 to the user-side devices 11-12.

Data sources 14-16 may be databases. The types of the data sources 14-16 may include: mysql, oracle, Hbase, Gbase, neo4j, ES, etc., which are not limited in this application. The business system 13 can be connected to one or more data sources, and specifically, the administrator of the business system 13 can manage the data sources according to actual business requirements. The data sources 14-16 are used to maintain physical data tables containing data resources, such as storage and management, and perform data interaction with the above-mentioned business system 13 to provide the above-mentioned target data resources that the business system 13 needs to query. Specifically, the data sources 14 - 16 may return the target data resources to the business system 13 according to the query action of the business system 13 .

In the related art, the business code of the business system 13 is used to directly look up the corresponding physical data table during the execution process, that is, the business system 13 is directly connected with the data sources 14-16, so that the business system 13 and the data sources 14-16 are directly connected. There is a coupling relationship between the physical data tables it maintains. Therefore, when the data source 14-16 is changed, for example, the change may be the deletion, addition or modification of the physical data table in the data source 14-16, or the addition of a new data source or the deletion of the original data source, etc. , may cause the original business code to fail to find the corresponding physical data table after execution, and thus fail to query the target data resource. Since the coupling between the business system 13 and the physical data tables in the data sources 14-16 is realized based on business codes deployed on the business system 13, new business codes need to be developed to be able to adapt to the above data source changes.

In view of the above problems, the embodiments of the present application provide a data resource query solution, which solves the problem that when the data source or the physical mapping table in the data source changes, it is possible to successfully query the target data resource without re-development of the business code. , which greatly reduces the development of business code and achieves the effect of reducing R&D costs.

FIG. 2 is a flowchart of a method for querying data resources provided by an exemplary embodiment. As shown in FIG. 2 , the method is applied to a business system (for example, the business system may be the business system 13 shown in FIG. 1 ). The method may include the following steps:

S101: In response to a query request of a query party for a target data resource, determine a target data resource entity corresponding to the target data resource.

In one embodiment, the query party may refer to an object that has a query requirement, such as a user, an application, or an AI program, which is not limited in this application. Specifically, the inquiring party can complete the inquiry process through the user-side devices 11-12 shown in FIG. 1 . The data resource that the queryer needs to query is the target data resource, and the type of the target data resource is often related to the actual application scenario, such as customer records, sales records, personnel records, purchase records, financial data, and inventory data. , this application does not limit it.

In one embodiment, the business system may provide the querying party with a query page, the page includes page elements corresponding to preset data resources, for example, the page elements may be virtual modules displayed on the page, and the page elements Or the description information of the data resource corresponding to the page element can be displayed nearby. For example, in a specific scenario, the query page can contain virtual modules that display the words "customer record", "sales record", "personnel record", etc. The query party can select the page element corresponding to the target data resource from all the page elements according to these words, and then trigger it by means of mouse click, touch and the like. The query request is generated by the query party triggering the page element corresponding to the target data resource.

A physical data table is maintained in the data source, and the physical data table is used to record corresponding data resources. The data resource entity may be a data object established locally in the business system, or may be a data object established on a third-party device other than the business system or the data source. The data object itself does not contain data resources, but there is a corresponding mapping relationship with the data resources.

For example, in some embodiments, when the user of the business system needs data resources related to "business status" that can be displayed on the user interface, the business configurator needs to add a data source that stores the corresponding data resources, such as data source A, data source Source B, and then create the data resource entities corresponding to the aforementioned data sources A and B. For example, the data resource entity corresponding to data source A is named "administrative license", and the data resource entity corresponding to data source B is named "foreign investment". Both of the two data resource entities are data resource entities corresponding to the relevant data resources required by the "operation status" module. Subsequently, the business configurator needs to establish the mapping relationship between the data resource entity and the data source, for example, establish the mapping relationship between "administrative license" and data source A, and establish the mapping relationship between "outbound investment" and data source B. After determining the data resource entity, the business system can determine the target data source based on the created mapping relationship, and then obtain the target data resource therefrom.

It should be explained that the configuration party of the above-mentioned business system refers to a person who can configure the business system. For example, the configuration party may be an administrator of the business system, or a user who has configuration rights and uses the business system. The user of the above-mentioned business system refers to the party using the business system. For example, the user may be a user of the business system or an administrator of the business system.

In some embodiments, the method for determining the target data resource entity corresponding to the target data resource may include the following steps A1-A2:

Step A1: Acquire configuration information of the target data resource according to the query request, where the configuration information includes a data resource entity ID.

The configuration information refers to some information required for acquiring the target data resource created by the service system configurator.

In some embodiments, the configuration information may be pre-generated and stored in the business system, and the business system may obtain different configuration information for different target data resources according to the query request.

In some embodiments, the configurator of the business system can perform custom configuration for the configuration information of the data resource on the page provided by the business system according to requirements.

For example, in a scenario where the user interface needs to display data resources related to "business status", the requirement is to obtain relevant data resources stored in different data sources for the "business status" resource, and assemble and generate pages according to a preset format for output. In this scenario, the user can configure the information displayed in the user interface according to the requirements, such as: module name, column name, text color, external link, page display style, etc., and can also configure the data resource entity ID, as in this scenario In is the ID of the data resource entity of "administrative license" and "foreign investment". It should be noted that the configuration information can include not only the ID of the data resource entity, but also other information such as "module content", "module type", "data list", "table name", etc. The configuration information can be used to obtain data or front-end pages. exhibit. The module content is the name of the page element corresponding to the preset data resource in the front-end page display. The module type is the template type of the custom configuration provided by the business application to the queryer, and the queryer can perform a certain degree of custom configuration on the basis of the template. The data list is the preset data resource corresponding to the page element in the front-end page display. The table name is the name of the data list. The above information is used for front-end page display. The data resource entity ID is used to get the data.

It should still be noted that the configuration information may be stored in the business application, or may be stored in other suitable places, such as a configuration center, such as a data resource entity.

Step A2: Determine the target data resource entity corresponding to the target data resource according to the data resource entity ID.

The ID of the data resource entity in the configuration information can be in one-to-one correspondence with the target data resource entity. Based on the data resource entity ID, the target data resource entity can be determined. The data resource entity ID is only an exemplary name of configuration information, and other configuration information with similar functions and characteristics should also be within the protection scope of this application.

In this application, the data resource entity determined by the business application based on the business code does not determine the physical data table in the data source based on the business code as in the related art. This makes it unnecessary to change the business code when the data source changes.

S102: Determine a target physical data table corresponding to the target data resource entity according to the stored mapping relationship between the data resource entity and the physical data table in the data source.

The physical data table in the embodiment of the present application is the carrier for recording data resources stored in the data source, and based on the type of data source, the form, format, and data storage method of the physical data table may be different. Of course, this difference No impact on this application. The physical data table is specifically used to establish a mapping relationship with the data resource entity in advance. When the business system queries the data source, the physical data table stored in the target data resource is determined, and the target data resource stored in the physical data table is returned to the business system.

The mapping relationship mentioned in this application is actually established between the data resource entity ID and the information on the physical data table, and the information on the corresponding physical data table can be found by virtue of the mapping relationship. The information on the above-mentioned physical data table includes information that can indicate the physical data table, such as the header of the physical data table, index information, and the like. According to the data resource entity ID, the mapping relationship of the data resource entity ID can be obtained, and then the target physical data table is found according to the mapping relationship, and the required target data resource is searched according to the physical data table.

When the business application receives the query request and determines the target data resource entity corresponding to the target data, the mapping relationship between the target data resource entity and the target physical data table in the data source can be determined. Further, the target physical data table corresponding to the target data can be determined through the mapping relationship.

It can be seen that there is a mapping relationship between the data resource entity and the physical data table in the data source. Therefore, when the data source changes, it is only necessary to establish a new mapping relationship between the data resource entity and the changed data source or physical data table to avoid In order to make changes to the code of the business application. Thereby, the technical effect of not having to develop new business codes and saving workload is realized.

In some embodiments, when the data source is changed, the service configuration party can update the mapping relationship between the stored data resource entity and the physical data table in the data source, so that the updated The mapping relationship can determine the updated target physical data table corresponding to the target data resource, so that the user can obtain the target data resource according to the determined target physical data table.

Therefore, when the data source is changed, it is only necessary to adjust the mapping relationship according to the change situation to ensure that the user can obtain the data normally, and the code of the business application does not need to be modified, thus saving workload. In addition, the user does not need to understand the data source, and does not need to have a deep understanding of the business. It is friendly to the user and improves the user experience.

In some embodiments, the situation that the data source is changed includes the situation that the data source corresponding to the data resource entity or the physical data table in the data source is added, deleted or replaced. For example, the physical data table in the data source corresponding to the original "administrative license" data entity has been added, deleted or replaced.

In this way, when the data resources are updated, the business system configuration party can add, delete or replace the data source or the physical data table in the data source in real time, so that the data resources can be updated in time, avoiding the data resources and the latest requirements of the users. The user has a bad experience due to matching, or the data is outdated and not updated.

S103: Acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party.

The present application provides a specific and implementable method for the above-mentioned acquisition of target data resources.

When the business system acquires the configuration information, the configuration information may include, in addition to the data resource entity ID, data resource description information pre-defined by the query party.

If there is no data resource description information pre-defined by the querying party in the configuration information, the physical data table is found through the data resource entity ID and the mapping relationship. When acquiring the target data resource in the physical data table, all or default data in the physical data table are acquired. target data resource. All or default target data resources obtained are returned to the business system, and the business system returns to the user-side device.

If the configuration information also includes the data resource description information pre-defined by the querying party, the physical data table is found by using the data resource entity ID and the mapping relationship. The pre-defined data resource description information matches the target data resource. The obtained matching target data resources are returned to the service system, and the service system returns to the user-side device.

It can be seen that the data resources stored in the physical data table can be screened and matched to a certain extent by virtue of the data resource description information predefined by the querying party, so that the querying party can obtain the required specific data resources through customization. It realizes the function that users can easily obtain data resources with different needs in different regions and industries.

After acquiring the target data resource, when the data resource is returned to the user-side device, the present application also provides a specific and implementable method to realize the function of customizing the front-end display page.

When the business system obtains the configuration information, the configuration information can include the front-end page display information pre-defined by the query party in addition to the data resource entity ID.

If there is no information displayed on the front-end page, after acquiring the target data resource, the business system directly returns the target data resource to the user-side device. At this time, the information displayed on the front-end page is the basic style originally set by the business system.

If the user needs to customize the front-end page display, and the configuration information includes the front-end page display information pre-defined by the queryer, after obtaining the target data resource, the business system assembles the target data resource according to the front-end page display information, and assembles the The target data resource after the information displayed on the front-end page is returned to the user-side device. The user-defined function of the display page is realized.

The above front-end page display information can include: text, color, width, table style, module name, etc. When the business system configures the data resources based on the front-end page display information, the front-end page information such as the font model, font color, font size, table presentation style, and name of the data resources when the data resources are displayed can be displayed in specific details. custom configuration.

In order to better understand the technical solution disclosed in the present application, the solution of the present application will be described below with reference to a specific embodiment. It should be noted that this embodiment is only exemplary and explanatory, and does not limit the present application.

The data query method of this embodiment is applied in a file management scenario of an enterprise. The file management scenario includes an interaction process between user-side devices, business systems, management centers, and data sources, which can be understood in conjunction with the multi-party interaction diagram in FIG. 3 . The management center stores the data resource entities constructed by the configurator, and the management center may be a third-party device outside the business system or data source. The data resource entity is the data object established in the management center.

Before using this method, the configurator of the business system needs to add a data source. The data source maintains a physical data table. The physical data table is used to record the corresponding data resources. The configurator also needs to build the data resource entity of the management center, and establish the data The mapping relationship between resource entities and physical data tables in the data source.

Virtual modules are displayed on the front-end page, and users can send query requests to business applications by triggering the virtual modules.

Specifically, a virtual module to be queried may contain multiple data resource entities, for example, the virtual module of "business status" to be queried by a user may contain two data resource entities of "administrative license" and "foreign investment". Regarding the construction mode of the module, this embodiment does not limit the present application.

The configurator can according to the user's demand for data resources, such as the need to query the data resources of the "business status" module, or the demand for the display style of the front-end page, such as module name, module type, column name, text color, external link , page display styles, etc., configure the virtual module of "business status" and the information of the corresponding data resource entities "administrative license" and "foreign investment" in advance, which is called configuration information. The configuration information may also include information for displaying the front-end page and information for obtaining data, and the configuration is customized by the user. For example, the module name, module type, column name, text color, external link, page display style, etc. used for front-end page display, such as the data resource entity ID and data resource description information used to obtain data. The module name is displayed on the interface, such as "basic information", "equity information", "business information", "business status", etc. The module type can include "basic type", "customized" and so on.

The following are the steps for specific data query.

S201: The business system provides a query page to the user-side device, and the page includes page elements corresponding to preset data resources.

The business application provides a query page to the user-side device of an enterprise, and the query page involves the display of virtual modules, such as basic information, business status, equity information, industrial and commercial information, and hazardous chemicals information.

S202: The user side device sends a query request to the service system.

For example, by triggering the "business status" module, the user sends a query request for the "business status" data resource to the business application.

S203: The business system queries configuration information.

The business application first queries the configuration information corresponding to "business status", which may include the stored data resource entity ID, for obtaining data resources. The data resource entity ID here is the ID of the data resource entity of "administrative permission" and "foreign investment" described above. It can also include information for front-end page display and data resource description information.

S204: The business system determines the data resource entity according to the data resource entity ID.

In this embodiment, the data resource entities of "administrative license" and "foreign investment" are determined by the data resource entity IDs of "administrative license" and "foreign investment".

S205: The management center returns the mapping relationship between the data resource entity and the physical data table in the data source to the business system.

In this embodiment, the management center is located on the device of the service application. Through the determined target data resource entity, the mapping relationship of the physical data table in the corresponding data source is found, and the mapping relationship is returned to the business application.

In another embodiment, the management center may be located on two different devices outside the service application, which is not limited in this application.

S206: The business system determines the physical data table in the data source based on the acquired mapping relationship.

In this embodiment, the physical data table referred to is the physical data table in which the target data resources of "administrative license" and "foreign investment" are stored.

S207: The business system acquires the matching target data resource in the physical data table according to the configuration information.

In this embodiment, the data resources in the physical data table are matched according to the specific content of the data resource description information in the configuration information, and the matched target data resources are returned to the business system.

S208: The business system assembles the target data resource according to the configuration information.

In this embodiment, after acquiring the target data resource, the target data resource can be assembled with the information used for displaying the front-end page in the configuration information.

S209: The business system returns the assembled target data resource to the user-side device.

In this embodiment, the assembled matched target data resource can be rendered into a table or list on the page, and displayed to the user.

Corresponding to the above embodiments of the data query method, the present application further provides an embodiment of a data query apparatus.

Please refer to FIG. 4 . FIG. 4 is a schematic structural diagram of an electronic device where a data query apparatus is located in an embodiment of the present application. At the hardware level, the device includes a processor 410, a network interface 420, a memory 430 and a non-volatile memory 440, and of course may also include hardware required by other services. One or more embodiments of the present application may be implemented based on software, for example, the processor 410 reads a corresponding computer program from the non-volatile memory 440 into the memory 430 and then executes it. Of course, in addition to software implementations, one or more embodiments of the present application do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subjects of the following processing procedures are not limited to each Logic unit, which can also be hardware or logic device.

Please refer to FIG. 5 , which is a block diagram of a data query apparatus according to an embodiment of the present application. The page access apparatus can be applied to the electronic device as shown in FIG. 4 to realize the technical solution of the present application. Wherein, the data query system is applied to a business system, and the cache data of the business system stores configuration information and a mapping relationship, which may include:

A query unit 510, configured to determine a target data resource entity corresponding to the target data resource in response to a query request by a query party for the target data resource;

a mapping unit 520, configured to determine a target physical data table corresponding to the target data resource entity according to the mapping relationship between the stored data resource entity and the physical data table in the data source;

The returning unit 530 is configured to acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party.

Optionally, also include:

The updating mapping unit 540 updates the mapping relationship between the stored data resource entity and the physical data table in the data source when the data source is changed.

Optionally, the change of the data source includes:

A data source or a physical data table in a data source has been added, deleted, or replaced.

Optionally, the query unit 510 is specifically used for:

Acquire configuration information of the target data resource according to the query request, where the configuration information includes a data resource entity ID;

The target data resource entity corresponding to the target data resource is determined according to the data resource entity ID.

Optionally, the configuration information further includes:

The data resource description information pre-defined by the query party; optionally, the returning unit 530 is specifically used for:

Acquire a data resource recorded in the target physical data table that matches the data resource description information as the target data resource.

Optionally, the configuration information further includes:

Front-end page display information pre-defined by the inquiring party; optionally, the returning unit 530 is specifically used for:

Perform data assembly on the target data resource according to the front-end page display information, and return the assembled target data resource to the query party.

Optionally, the query unit 510 is specifically used for:

providing a query page to the query party, the page including page elements corresponding to preset data resources;

The query request is generated by the query party triggering the page element corresponding to the target data resource.

In this embodiment, the query unit can be used to:

In response to the query request for the target data resource by the query party, the configuration information is acquired based on the query request, and the data resource entity ID in the configuration information is determined to determine the target data resource entity corresponding to the target data resource.

The mapping unit can be specifically used for:

According to the mapping relationship between the stored data resource entity and the physical data table in the data source, and according to the determined data resource entity, the target physical data table stored in the data source corresponding to the target data resource entity is determined.

The returning unit can be specifically used for:

Obtain the target data resource that matches the configuration information in the physical data table, return the target data resource to the business system, and the business system assembles the target data resource according to the configuration information, and returns the assembled target data resource to the inquiring party.

For details of the implementation process of the functions and functions of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method, which will not be repeated here.

As for the apparatus embodiments, since they basically correspond to the method embodiments, reference may be made to some descriptions of the method embodiments for related instructions. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in a local, or it can be distributed over multiple network elements. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present application. Those of ordinary skill in the art can understand and implement it without creative effort.

In the 1990s, improvements in a technology could be clearly differentiated between improvements in hardware (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvements in method flow). However, with the development of technology, the improvement of many methods and processes today can be regarded as a direct improvement of the hardware circuit structure. Designers almost get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware entity modules. It should also be clear to those skilled in the art that a hardware circuit for implementing the logic method process can be easily obtained by simply programming the method process in the above-mentioned several hardware description languages and programming it into the integrated circuit.

The controller can be implemented in any suitable manner, and those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, the controller can be implemented in logic gates, switches, special-purpose functions by logically programming the method steps. Integrated circuits, programmable logic controllers and embedded microcontrollers, etc., to achieve the same function. Therefore, such a controller can be regarded as a hardware component, and the devices included therein for realizing various functions can also be regarded as a structure within the hardware component. Or even, the means for implementing various functions can be regarded as both a software module implementing a method and a structure within a hardware component.

The systems, devices, modules or units described in the above embodiments may be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, this application does not exclude that with the development of computer technology in the future, the computer that realizes the functions of the above embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, or a personal digital assistant. , media players, navigation devices, email devices, game consoles, tablets, wearables, or a combination of any of these devices.

Although one or more embodiments of the present application provide method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-inventive means. The sequence of steps enumerated in the embodiments is only one of the execution sequences of many steps, and does not represent the only execution sequence. When an actual device or terminal product is executed, it can be executed sequentially or in parallel according to the methods shown in the embodiments or the drawings (eg, a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, product or device comprising a list of elements includes not only those elements, but also others not expressly listed elements, or also include elements inherent to such a process, method, product or device. Without further limitation, it does not preclude the presence of additional identical or equivalent elements in a process, method, product or apparatus comprising the stated elements. For example, words such as first, second, etc. are used to denote names and do not denote any particular order.

For the convenience of description, when describing the above device, the functions are divided into various modules and described respectively. Of course, when implementing one or more of this application, the functions of each module can be implemented in the same one or more software and/or hardware, and the modules that implement the same function can also be implemented by a combination of multiple sub-modules or sub-units, etc. . The apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-persistent memory in computer readable media, random access memory (RAM) and/or non-volatile memory in the form of, for example, read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by computing devices. Computer-readable media, as defined herein, excludes transitory computer-readable media, such as modulated data signals and carrier waves.

As will be appreciated by those skilled in the art, one or more embodiments of the present application may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present application may employ a computer program implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein form of the product.

One or more embodiments of the present application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this application is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the partial descriptions of the method embodiments. In the description of this application, references to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc. refer to the specific features described in connection with the embodiment or example. , structure, material or feature is included in at least one embodiment or example of the present application. In this application, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine the different embodiments or examples described in this application, as well as the features of the different embodiments or examples, without conflicting each other.

The above descriptions are merely examples of one or more embodiments of the present application, and are not intended to limit the one or more embodiments of the present application. Various modifications and variations of the one or more embodiments of the present application may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims.

Claims (10)

1. a data resource query method, is characterized in that, comprises: In response to a query request for a target data resource by a query party, determining a target data resource entity corresponding to the target data resource; According to the mapping relationship between the stored data resource entity and the physical data table in the data source, determine the target physical data table corresponding to the target data resource entity; Acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party. 2. The method of claim 1, further comprising: When the data source is changed, the mapping relationship between the stored data resource entity and the physical data table in the data source is updated. 3. The method according to claim 2, wherein the data source is changed, comprising: A data source or a physical data table in a data source has been added, deleted, or replaced. 4. The method according to claim 1, wherein the determining the target data resource entity corresponding to the target data resource comprises: Acquire configuration information of the target data resource according to the query request, where the configuration information includes a data resource entity ID; The target data resource entity corresponding to the target data resource is determined according to the data resource entity ID. 5 . The method according to claim 4 , wherein the configuration information further includes data resource description information pre-defined by the query party; the acquisition of the data recorded in the target physical data table Target data resources, including: Acquire a data resource recorded in the target physical data table that matches the data resource description information as the target data resource. 6 . The method according to claim 4 , wherein the configuration information further comprises front-end page display information pre-defined by the inquiring party; the returning the target data resource to the inquiring party, include: Perform data assembly on the target data resource according to the front-end page display information, and return the assembled target data resource to the query party. 7. The method of claim 1, further comprising: providing a query page to the query party, where the query page includes page elements corresponding to preset data resources; The query request is generated by the query party triggering the page element corresponding to the target data resource. 8. A device for querying data resources, comprising: a query unit, configured to determine a target data resource entity corresponding to the target data resource in response to a query request by a query party for the target data resource; a mapping unit, configured to determine a target physical data table corresponding to the target data resource entity according to the mapping relationship between the stored data resource entity and the physical data table in the data source; The returning unit is configured to acquire the target data resource recorded in the target physical data table, and return the target data resource to the query party. 9. An electronic device, comprising: a processor and a memory; the memory for storing computer programs; The processor is configured to execute the data resource query method according to any one of claims 1-7 by invoking the computer program. 10. A computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the data resource query method according to any one of claims 1-7 is implemented.

Images