CN111625548A - Query method, system, device and computer readable medium - Google Patents
Query method, system, device and computer readable medium Download PDFInfo
- Publication number
- CN111625548A CN111625548A CN201910146940.4A CN201910146940A CN111625548A CN 111625548 A CN111625548 A CN 111625548A CN 201910146940 A CN201910146940 A CN 201910146940A CN 111625548 A CN111625548 A CN 111625548A
- Authority
- CN
- China
- Prior art keywords
- attribute value
- data
- query
- service
- personalized interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012795 verification Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 2
- 230000000875 corresponding effect Effects 0.000 description 43
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 230000009471 action Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000001276 controlling effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a query method, a system, a device and a computer readable medium. The query system includes: UI component module and subassembly reference module, UI component module includes: the query engine is used for retrieving the application metadata and acquiring a personalized interface corresponding to the user identifier; the template unit comprises a plurality of personalized interfaces, each personalized interface comprises a plurality of controls, at least one control sends an attribute value query request, and the attribute value of at least one control in the plurality of controls is organized according to the returned attribute value data; a component reference module comprising: the service routing unit is used for retrieving the service metadata and transferring the retrieval result and the attribute value query request to the service execution unit; and the service execution unit is used for calling the corresponding data service to obtain the attribute value data. The query system adopts application metadata to manage a personalized interface and adopts service metadata to manage data service, thereby realizing the expansion function of a system interface and a bottom layer architecture.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a query method, a query system, a query device, and a computer-readable medium.
Background
The SaaS service model is very different from the traditional license model software, and the current architecture of SaaS changes from delivering software to multiple tenants to providing Web solutions to multiple tenants. The main advantage of multi-tenancy is cost-efficiency. Sharing software, hardware, application development and maintenance costs among multiple tenants may reduce the cost per tenant. Moreover, sharing instances of an application among tenants may provide other benefits, e.g., when an application is upgraded, all tenants may be upgraded at the same time.
As a background above, many problems will also arise. The requirements of multiple tenants for software are both the same and different. However, how to satisfy the requirements of all tenants and save the cost to the maximum extent through a unified WEB solution is a problem worthy of industrial research. For example, how to provide a uniform query system for multiple tenants, in the query system, the content of the retrieval interface of different tenants is different, the data source to be retrieved is different, and the retrieval mode is also different.
Disclosure of Invention
In view of the above problems, the present invention provides a unified query system, which satisfies different search requirements of multiple tenants.
According to a first aspect of the present invention, there is provided a query system comprising: a UI component module and a component reference module,
the UI component module includes:
the query engine is used for retrieving application metadata according to the user identification to obtain an individualized interface corresponding to the user identification, and the application metadata stores the corresponding relation between the user identification and the individualized interface;
the template unit comprises a plurality of personalized interfaces, each personalized interface comprises a plurality of controls, at least one of the controls sends an attribute value query request, and the attribute value of at least one of the controls is organized according to the returned attribute value data;
a component reference module comprising:
the service routing unit retrieves service metadata according to the user identifier and transfers a retrieval result and the attribute value query request to the service execution unit;
and the service execution unit calls a corresponding data service according to the attribute value query request and the retrieval result to obtain the attribute value data.
Optionally, the query system further comprises: and the interface loading module is used for loading the personalized interface, and when the personalized interface is loaded, at least one control in the plurality of controls of the personalized interface sends a property value query request.
Optionally, the component reference module further includes an identity verification unit, where the identity verification unit is configured to verify a user identity corresponding to the user identifier.
Optionally, the component referencing module further includes a caching unit, and the caching unit is configured to cache the attribute value data.
Optionally, the service execution unit preferentially retrieves the cache to obtain the attribute value data, and invokes a corresponding data service when the cache does not contain the attribute value data.
Optionally, the component reference module further includes a data authority processing unit, where the data authority processing unit is configured to determine, according to the user identifier, a data authority corresponding to the user identifier.
Optionally, the service execution unit controls the returned attribute value data according to the data authority corresponding to the user identifier.
Optionally, the service execution unit generates query SQL according to the attribute value query request and the data permission corresponding to the user identifier, and the data permission corresponding to the user identifier is converted into a where condition of the query SQL.
Optionally, the query system further comprises: the interface customizing module is used for customizing the personalized interface according to the standard template and adding the association relationship between the personalized interface and the user identification into the application metadata.
According to a second aspect of the embodiments of the present invention, there is provided a query method, including:
receiving an application request, wherein the application request comprises a user identifier;
retrieving application metadata based on the user identifier, and obtaining a personalized interface corresponding to the user identifier, wherein the application metadata stores the corresponding relation between the user identifier and the personalized interface, and the personalized interface comprises a plurality of controls;
retrieving service metadata according to the user identification to obtain a retrieval result;
calling corresponding data service according to the retrieval result and the attribute value query request to execute the attribute value query request and obtain a corresponding attribute value;
adding the respective property value to a property value of at least one of the plurality of controls.
Optionally, the query method further includes: and loading the personalized interface, and triggering at least one control in a plurality of controls of the personalized interface to send a property value query request when the personalized interface is loaded.
Optionally, the query method further includes: and checking the user identity corresponding to the user identification.
Optionally, the query method further includes: the attribute value data is cached.
Optionally, the query method further includes: and preferentially acquiring the attribute value data from the cache, and calling corresponding data service when the cache does not contain the attribute value data.
Optionally, the query method further includes: and determining the data authority corresponding to the user identification according to the user identification.
Optionally, the query method further includes: and controlling the attribute value data returned to at least one control of the plurality of controls according to the data authority corresponding to the user identification.
Optionally, the controlling, according to the data authority corresponding to the user identifier, the attribute value data returned to at least one of the plurality of controls includes: and generating query SQL according to the attribute value query request and the data authority corresponding to the user identification, wherein the data authority corresponding to the user identification is converted into a where condition of the query SQL.
Optionally, the query method further includes: and customizing the personalized interface according to a standard template, and adding the association relationship between the personalized interface and the user identifier into the application metadata.
According to a third aspect of embodiments of the present invention, there is provided a computer-readable storage medium storing computer instructions that, when executed, implement the query method of any one of the above.
According to a fourth aspect of the embodiments of the present invention, there is provided an inquiry apparatus, including:
a memory for storing computer instructions;
a processor coupled to the memory, the processor configured to perform a query method implementing any of the above based on computer instructions stored by the memory.
One embodiment of the present invention has the following advantages or beneficial effects: and managing the corresponding relation between the personalized interface and the user identification by adopting the application metadata, and managing the corresponding relation between the data service and the user identification by adopting the service metadata, thereby realizing the extended functions of the system interface and the bottom layer architecture. And moreover, the data service is managed by adopting the service metadata, and when a new tenant is added, the service built for the tenant does not influence the running business of other tenants.
Furthermore, the personalized interface is customized according to the standard template, the standard template comprises a plurality of controls, the personalized interface can be customized through a dragging mode, the customizing process is simple and convenient, and therefore the expansion of the system interface is facilitated.
Drawings
The above and other objects, features and advantages of the present invention will become more apparent by referring to the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a query system according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a query system according to another embodiment of the present invention;
FIG. 3 is a flow diagram illustrating the creation and display of a personalized interface according to one embodiment of the invention;
FIG. 4 illustrates a flow diagram of a query method of one embodiment of the invention;
FIG. 5 shows a flow diagram of a query method of another embodiment of the invention;
fig. 6 shows a block diagram of an inquiry apparatus of an embodiment of the present invention.
Detailed Description
Various embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Like elements in the various figures are denoted by the same or similar reference numerals. For purposes of clarity, the various features in the drawings are not necessarily drawn to scale. Moreover, certain well-known elements may not be shown in the figures.
Fig. 1 shows a schematic structural diagram of a query system according to an embodiment of the present invention. As shown, the query system includes a UI component module 100 and a component reference module 200.
The UI component module 100 mainly contains functional modules related to the UI. The UI component module 100 is further divided into a query engine 101, a template unit 102, and application metadata 103.
The application metadata 103 represents the correspondence of the user identification and the personalized interface. The user identification uniquely identifies a tenant. As described in the background, tenants may share instances of an application. However, the query system provided by the invention needs to provide different query interfaces and functions for each tenant, so that different tenants need to be distinguished. The personalized interface is a personalized query interface established for each tenant. The application metadata 103 is typically stored and managed using a structured database management system, such as MySQL, ORACLE.
For a user request of a tenant, the query engine 101 parses the user request to obtain a user identifier, retrieves application metadata according to the user identifier, obtains a name of a personalized interface corresponding to the user identifier, and further obtains the personalized interface from a repository of the personalized interface. The plurality of personalized interfaces is stored, for example, in a file library of the template unit 102 as shown.
The template unit 102 is configured to store a plurality of personalized interfaces, each personalized interface including a plurality of controls. Here, a control refers to the encapsulation of a component on an interface. Components on the interface include buttons, multiple-choice or single-choice list boxes, edit boxes, static text in a dialog box, and so forth. The properties in the control may correspond to the properties of the component, and the method in the control may be set as a method for operations such as reading and writing of the properties of the component, so that the component can be managed by the control. The property values of some of the properties of the components are static, for example, buttons, and the property values of some of the properties are dynamic, for example, a drop-down list for representing the commodity class, the commodity class in the e-commerce system changes continuously, so that the commodity class data in the drop-down list must be obtained from the database in real time, and therefore the control of the component with the dynamic property value provides a method for obtaining the property values. The method submits a property value query request and organizes the property values of the components in the control based on the returned property value data.
The component reference module 200 mainly contains functional modules related to business logic. The component reference module 200 further comprises a service routing unit 201 and a service execution unit 202.
The service routing unit 201 retrieves the service metadata 210 according to the user identifier according to the received attribute value query request, and forwards the retrieval result and the attribute value query request to the service execution unit. The user id is from UI component module 100, and is transmitted as an input parameter when UI component module 100 calls an interface in component reference module 200, for example. The service metadata 201 represents a correspondence between a data service and a user identification.
The service execution unit 202 invokes a corresponding data service according to the attribute value query request and the retrieval result of the service metadata to obtain attribute value data. As shown, the main data service 301, the inventory service 303, and the organization service 302 each represent one data service. The master data service 301 manages data requests including brands, categories, etc. The inventory service 303 manages data requests for inventory item types, inventory categories, and the like. The organization service 302 manages data requests such as department data. Multiple data services may be deployed on a distributed system, for example, a data service for an a tenant is deployed on server 1, and a service execution unit for a B tenant is deployed on server 2.
In the embodiment of the invention, the corresponding relation between the personalized interface and the user identification is managed by adopting the application metadata, and the corresponding relation between the data service and the user identification is managed by adopting the service metadata, so that the expansion functions of the system interface and the bottom layer framework are realized. And the data service is managed by adopting the service metadata, so that when the data service is built for a new tenant, the running business of other tenants cannot be influenced.
In an optional embodiment, the query system further includes: and the interface loading module (not shown in the figure) is used for loading the personalized interface, and when the personalized interface is loaded, at least one control in the plurality of controls in the personalized interface sends the attribute value query request and the user identification.
Fig. 2 is a schematic structural diagram of a query system according to another embodiment of the present invention. The service metadata 210 in fig. 1 is not shown in the figure. The difference from the embodiment shown in fig. 1 is that the component reference module 200 further includes an identity checking unit 203, a caching unit 204, and a data right processing unit 205.
The identity verification module 203 is used for completing the verification of the user identity by adopting a certain means. For example, the user identity is checked according to the transmitted user identification to determine whether the user identity is a lessee in the system or whether the lessee identity of the lessee is still in the validity period. In order to ensure the identity of the tenant, the user identification may also be encrypted and decrypted using an asymmetric encryption algorithm. In an alternative example, the identity verification module 203 uses an external authentication platform 300 to verify the identity of the tenant.
The cache unit 204 is used to cache attribute value data. The service execution unit 202 stores the obtained attribute value data in the cache, preferentially retrieves the cache when the attribute value query request is executed next time, and recalls the corresponding data service to obtain the attribute value data when the corresponding attribute value data does not exist in the cache. Optionally, the query system of this embodiment further includes a synchronization unit (not shown in the figure), and the synchronization unit is configured to update the data in the cache at regular time.
The data authority processing unit 205 is configured to determine a data authority corresponding to a tenant according to the user identifier. For example, when an application is customized for a tenant, a data service that the tenant has an authority to access may be designated, and further, a data record that the tenant has an authority to use may be designated. The service execution unit 202 controls the attribute value data returned to the control according to the data authority corresponding to the user identifier. In one example, the service execution unit 202 converts the corresponding data rights into a where condition when generating the query SQL. For example, the order has fields for dealer (customer), inventory (inv), etc. There is a need to limit a user to only being able to query specific dealers and specific inventory orders. Tenant A, with its authorized dealers C1, C2, C3 and its authorized inventory I1, I2, I3, then when tenant A performs a query operation on an order, whatever the conditions it sets, the final query SQL must be accompanied by the following SQL statements:
(custom is null or custom in('C1'，'C2'，'C3'))and(inv is null orcustom in('I1'，'I2'，'I3))。
according to the embodiments, the configuration mode is provided through the query engine, and the requirements of the personalized query service of a plurality of lessees are met. The underlying framework based on the metadata can ensure that the instances of other tenants are not influenced on the basis of providing personalized services for the tenants. It is appreciated that multiple tenants share a query instance and that when an application is upgraded, multiple tenants upgrade simultaneously.
FIG. 3 is a flow chart illustrating the process of creating and displaying a personalized interface according to an embodiment of the invention.
Referring to fig. 3, the process of making and displaying the personalized interface includes three stages: a design phase 301, a configuration phase 302, and an execution phase 303. The pre-fabricated metadata 310 is included in the design phase. The pre-formed metadata 310 includes defining and encoding various controls, components, making standard templates from the controls and/or components, designing data structures for application metadata and service metadata, and the like. The configuration phase 303 configures an interface and a service running in the background for a new tenant, thereby opening up the business processes of the front end and the back end. Specifically, a personalized interface is created according to the requirements of a tenant (step 320), interface attributes are maintained (step 330), the completed personalized interface is assigned to the tenant (step 350), and the corresponding relationship between the tenant and the personalized interface is added to the application metadata (step 350). In the execution phase 303, firstly, the tenant submits a browsing request (i.e., step 360), and after the query system receives the request, the query engine is invoked (i.e., step 370), and the query engine first determines whether a personalized interface exists (i.e., step 380), if the personalized interface does not exist, the standard template is loaded (i.e., step 390), and if the personalized interface exists, the personalized interface is loaded (i.e., step 500). In order to conveniently manufacture the personalized interface, preferably, a standard template is displayed, a development component and a control are dragged, rapid development and application are realized, development efficiency is improved, unified styles and functional componentization are realized, and later maintenance cost is reduced.
In summary, the query system may further include an interface customization module, configured to customize a personalized interface according to the standard template, and add an association relationship between the personalized interface and the user identifier to the application metadata.
Referring to fig. 4, fig. 4 is a schematic structural diagram illustrating an application of the query system of the embodiment of the present invention to a financial system 401 and a basic data system 402. Referring to fig. 4, the query interface of the finance system 401 needs to load creator information, the finance system simply stores ID, the creator information is provided by the basic data domain service 403 and the ES search service 404, and thus the application reference component module 200 is required to forward the data request to a specific service. Specifically, the application reference module 200 queries the cache first, and if no corresponding data exists in the cache, the application reference module forwards the data to a specific data service, and the data service is responsible for retrieving the data and updating the data into the cache. Similarly, the basic information of the provider needs to be forwarded to a specific service by referring to the component module 200, and the basic information of the provider such as the code, name, etc. of the provider is provided by the basic data field service 403 and the ES search service 404. In addition, the reimbursement bill interface 4011 and the material interface 4021 in the financial system 401 are personalized interfaces obtained based on the embodiments of the present invention.
FIG. 5 shows a flow diagram of a query method of one embodiment of the invention. The method specifically comprises the following steps.
In step S501, an application request is received, where the application request includes a user identifier.
In step S502, application metadata is retrieved based on the user identifier, and a personalized interface corresponding to the user identifier is obtained.
In step S503, the service metadata is retrieved according to the user identifier, and a retrieval result is obtained.
In step S504, a corresponding data service is called according to the retrieval result and the attribute value query request to execute the attribute value query request and obtain a corresponding attribute value.
In step S505, the corresponding property value is added to the property value of at least one of the plurality of controls.
In the query method of the embodiment, the personalized interface is managed based on the application metadata, and the data service is managed based on the service metadata, so that the expansion functions of the system interface and the bottom layer architecture are realized. When an application requests a personalized interface, the corresponding personalized interface is found according to a user identifier, the personalized interface is loaded, an attribute value query request is sent according to attribute values of a plurality of controls contained in the personalized interface, service metadata is retrieved according to the user identifier, the attribute query request is executed by the corresponding data service, and returned attribute value data are returned to the controls, so that the loading of the personalized interface is completed. It can be understood that if the attribute value retrieval method is included in the design of the control, when the personalized interface is loaded, the control is triggered to send an attribute value query request, and attribute value data is returned to the control for filling the attribute value of the control. A typical example is a supplier list, and when the interface is loaded, the supplier data in the list is obtained from the supplier base data.
In an optional embodiment, the query method further includes completing verification of the user identity by a certain means. The user here corresponds to the tenant described above. For example, whether the tenant in the system is determined according to the transmitted user identification or whether the tenant identity of the tenant is still in the validity period. In order to ensure the identity of the tenant, the user identification may also be encrypted and decrypted using an asymmetric encryption algorithm.
In an alternative embodiment, the attribute value data obtained from each data service is stored in a cache and updated in real time using a synchronization process. In this way, when the same attribute value data is required to be used by the subsequent application or another application, the subsequent application or another application can preferentially read the attribute value data from the cache.
In an alternative embodiment, data permissions are set and the range of data that a user can use is checked for a user request. One convenient way is to translate the data permissions into where conditions in query SQL.
Fig. 6 shows a block diagram of an inquiry apparatus of an embodiment of the present invention. The apparatus shown in fig. 6 is only an example and should not limit the functionality and scope of use of embodiments of the present invention in any way.
Referring to fig. 6, the inquiry apparatus 60 includes a processor 601, a memory 602, and an input-output device 603 connected by a bus. The memory 602 includes a Read Only Memory (ROM) and a Random Access Memory (RAM), and various computer instructions and data required to perform system functions are stored in the memory 602 and read by the processor 601 from the memory 602 to perform various appropriate actions and processes. An input portion 5 of an input/output device including a keyboard, a mouse, and the like; an output section including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section including a hard disk and the like; and a communication section including a network interface card such as a LAN card, a modem, or the like. The memory 602 also stores the following computer instructions to perform the operations specified by the query method of embodiments of the present invention: receiving an application request, wherein the application request comprises a user identifier; retrieving application metadata based on the user identifier, and obtaining a personalized interface corresponding to the user identifier, wherein the application metadata stores the corresponding relation between the user identifier and the personalized interface, and the personalized interface comprises a plurality of controls; retrieving service metadata according to the user identification to obtain a retrieval result; calling corresponding data service according to the retrieval result and the attribute value query request to execute the attribute value query request and obtain a corresponding attribute value; adding the respective property value to a property value of at least one of the plurality of controls.
Accordingly, an embodiment of the present invention provides a computer-readable storage medium, which stores computer instructions that, when executed, implement the operations specified by the above-mentioned consulting volume prediction method.
The flowcharts and block diagrams in the figures and block diagrams illustrate the possible architectures, functions, and operations of the systems, methods, and apparatuses according to the embodiments of the present invention, and may represent a module, a program segment, or merely a code segment, which is an executable instruction for implementing a specified logical function. It should also be noted that the executable instructions that implement the specified logical functions may be recombined to create new modules and program segments. The blocks of the drawings, and the order of the blocks, are thus provided to better illustrate the processes and steps of the embodiments and should not be taken as limiting the invention itself.
The various modules or units of the system may be implemented in hardware, firmware or software. The software includes, for example, a code program formed using various programming languages such as JAVA, C/C + +/C #, SQL, and the like. Although the steps and sequence of steps of the embodiments of the present invention are presented in method and method diagrams, the executable instructions of the steps implementing the specified logical functions may be re-combined to create new steps. The sequence of the steps should not be limited to the sequence of the steps in the method and the method illustrations, and can be modified at any time according to the functional requirements. Such as performing some of the steps in parallel or in reverse order.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
While embodiments in accordance with the invention have been described above, these embodiments are not intended to be exhaustive or to limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. The invention is limited only by the claims and their full scope and equivalents.
Claims (20)
1. A query system, comprising: a UI component module and a component reference module,
the UI component module includes:
the query engine is used for retrieving application metadata according to the user identification to obtain a personalized interface corresponding to the user identification, wherein the application metadata represents the corresponding relation between the user identification and the personalized interface;
the template unit comprises a plurality of personalized interfaces, each personalized interface comprises a plurality of controls, at least one of the controls sends an attribute value query request, and the attribute value of at least one of the controls is organized according to the returned attribute value data;
a component reference module comprising:
the service routing unit retrieves service metadata according to the user identifier and transfers a retrieval result and the attribute value query request to the service execution unit;
and the service execution unit calls a corresponding data service according to the attribute value query request and the retrieval result to obtain the attribute value data.
2. The query system of claim 1, further comprising: and the interface loading module is used for loading the personalized interface, and when the personalized interface is loaded, at least one control in the plurality of controls of the personalized interface sends a property value query request.
3. The query system of claim 1, wherein the component referencing module further comprises an identity verification unit, and the identity verification unit is configured to verify a user identity corresponding to the user identifier.
4. The query system of claim 1, wherein said component referencing module further comprises a caching unit for caching said attribute value data.
5. The query system according to claim 4, wherein said service execution unit preferentially retrieves a cache for obtaining said attribute value data, and calls a corresponding data service when said attribute value data is not contained in the cache.
6. The query system of claim 1, wherein the component referencing module further comprises a data permission processing unit, and the data permission processing unit is configured to determine the data permission corresponding to the user identifier according to the user identifier.
7. The query system of claim 6, wherein the service execution unit controls the returned attribute value data according to a data authority corresponding to the user identifier.
8. The query system according to claim 7, wherein the service execution unit generates a query SQL according to the attribute value query request and the data permissions corresponding to the user identifier, and the data permissions corresponding to the user identifier are converted into where conditions of the query SQL.
9. The query system of claim 1, further comprising: the interface customizing module is used for customizing the personalized interface according to the standard template and adding the association relationship between the personalized interface and the user identification into the application metadata.
10. A method of querying, comprising:
receiving an application request, wherein the application request comprises a user identifier;
retrieving application metadata based on the user identifier, and obtaining a personalized interface corresponding to the user identifier, wherein the application metadata stores the corresponding relation between the user identifier and the personalized interface, and the personalized interface comprises a plurality of controls;
retrieving service metadata according to the user identification to obtain a retrieval result;
calling corresponding data service according to the retrieval result and the attribute value query request to execute the attribute value query request and obtain a corresponding attribute value;
adding the respective property value to a property value of at least one of the plurality of controls.
11. The method of querying as claimed in claim 10, further comprising: and loading the personalized interface, and triggering at least one control in a plurality of controls of the personalized interface to send a property value query request when the personalized interface is loaded.
12. The method of querying as claimed in claim 10, further comprising: and checking the user identity corresponding to the user identification.
13. The method of querying as claimed in claim 10, further comprising: the attribute value data is cached.
14. The method of querying as claimed in claim 13, further comprising: and preferentially acquiring the attribute value data from the cache, and calling corresponding data service when the cache does not contain the attribute value data.
15. The method of querying as claimed in claim 10, further comprising: and determining the data authority corresponding to the user identification according to the user identification.
16. The method of querying as claimed in claim 15, further comprising: and controlling the attribute value data returned to at least one control of the plurality of controls according to the data authority corresponding to the user identification.
17. The query method of claim 16, wherein the controlling the attribute value data returned to at least one of the plurality of controls according to the data authority corresponding to the user identifier comprises: and generating query SQL according to the attribute value query request and the data authority corresponding to the user identification, wherein the data authority corresponding to the user identification is converted into a where condition of the query SQL.
18. The method of querying as claimed in claim 10, further comprising: and customizing the personalized interface according to a standard template, and adding the association relationship between the personalized interface and the user identifier into the application metadata.
19. A computer-readable storage medium storing computer instructions which, when executed, implement the query method of any one of claims 9 to 18.
20. An inquiry apparatus, comprising:
a memory for storing computer instructions;
a processor coupled to the memory, the processor configured to perform implementing the query method of any of claims 9-18 based on computer instructions stored by the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910146940.4A CN111625548A (en) | 2019-02-27 | 2019-02-27 | Query method, system, device and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910146940.4A CN111625548A (en) | 2019-02-27 | 2019-02-27 | Query method, system, device and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111625548A true CN111625548A (en) | 2020-09-04 |
Family
ID=72272408
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910146940.4A Pending CN111625548A (en) | 2019-02-27 | 2019-02-27 | Query method, system, device and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111625548A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221896A1 (en) * | 2022-05-16 | 2023-11-23 | 卡奥斯化智物联科技(青岛)有限公司 | Chemical-field-based information query method, apparatus and device, and storage medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040111728A1 (en) * | 2002-12-05 | 2004-06-10 | Schwalm Brian E. | Method and system for managing metadata |
| US20070180066A1 (en) * | 2001-03-02 | 2007-08-02 | Theresa Sherwood | System and method for searching data partially displayed on a user interface |
| US20070180386A1 (en) * | 2001-03-02 | 2007-08-02 | Alan Ballard | Customization of user interface presentation in an internet application user interface |
| US20080163088A1 (en) * | 2006-12-29 | 2008-07-03 | Aurobinda Pradhan | System and method for managing browser extensions |
| CN101350023A (en) * | 2008-08-29 | 2009-01-21 | 北京航空航天大学 | Method and platform capable of customizing enquiry based on service combination |
| CN101833568A (en) * | 2010-04-01 | 2010-09-15 | 武汉大学 | Web data management system |
| CN101894171A (en) * | 2010-02-05 | 2010-11-24 | 刘剑 | Precise information service system and method |
| US20120239519A1 (en) * | 2011-03-15 | 2012-09-20 | Ebay Inc. | Personalizing search results |
| US20150007169A1 (en) * | 2013-06-26 | 2015-01-01 | International Business Machines Corporation | Deploying an application in a cloud computing environment |
| CN105677745A (en) * | 2015-12-28 | 2016-06-15 | 国云科技股份有限公司 | General efficient self-service data search system and implementation method |
| CN108536778A (en) * | 2018-03-29 | 2018-09-14 | 客如云科技（成都）有限责任公司 | A kind of data application shared platform and method |
-
2019
- 2019-02-27 CN CN201910146940.4A patent/CN111625548A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070180066A1 (en) * | 2001-03-02 | 2007-08-02 | Theresa Sherwood | System and method for searching data partially displayed on a user interface |
| US20070180386A1 (en) * | 2001-03-02 | 2007-08-02 | Alan Ballard | Customization of user interface presentation in an internet application user interface |
| US20040111728A1 (en) * | 2002-12-05 | 2004-06-10 | Schwalm Brian E. | Method and system for managing metadata |
| US20080163088A1 (en) * | 2006-12-29 | 2008-07-03 | Aurobinda Pradhan | System and method for managing browser extensions |
| CN101350023A (en) * | 2008-08-29 | 2009-01-21 | 北京航空航天大学 | Method and platform capable of customizing enquiry based on service combination |
| CN101894171A (en) * | 2010-02-05 | 2010-11-24 | 刘剑 | Precise information service system and method |
| CN101833568A (en) * | 2010-04-01 | 2010-09-15 | 武汉大学 | Web data management system |
| US20120239519A1 (en) * | 2011-03-15 | 2012-09-20 | Ebay Inc. | Personalizing search results |
| US20150007169A1 (en) * | 2013-06-26 | 2015-01-01 | International Business Machines Corporation | Deploying an application in a cloud computing environment |
| CN105677745A (en) * | 2015-12-28 | 2016-06-15 | 国云科技股份有限公司 | General efficient self-service data search system and implementation method |
| CN108536778A (en) * | 2018-03-29 | 2018-09-14 | 客如云科技（成都）有限责任公司 | A kind of data application shared platform and method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221896A1 (en) * | 2022-05-16 | 2023-11-23 | 卡奥斯化智物联科技(青岛)有限公司 | Chemical-field-based information query method, apparatus and device, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11615142B2 (en) | Mapping and query service between object oriented programming objects and deep key-value data stores | |
| AU2019291942B2 (en) | Custom interactions with visualizations | |
| US8332359B2 (en) | Extended system for accessing electronic documents with revision history in non-compatible repositories | |
| US9208212B2 (en) | Field extensibility in a multi-tenant environment with columnar database support | |
| AU2019291940B2 (en) | Visualization customization | |
| US10467200B1 (en) | Techniques for dynamic data processing | |
| AU2019295794B2 (en) | Autolayout of visualizations based on contract maps | |
| US8578278B2 (en) | Dynamic user interface content adaptation and aggregation | |
| US9298729B2 (en) | Plural architecture master data management | |
| US9164776B2 (en) | Dynamic determination of navigation targets in a flexible user interface environment | |
| US11593324B2 (en) | Reversible data transforms | |
| AU2020298056B2 (en) | Autolayout of visualizations based on graph data | |
| US20080104008A1 (en) | Common data broker method, system, and program product | |
| US20140114916A1 (en) | Code generation and implementation method, system, and storage medium for delivering bidirectional data aggregation and updates | |
| US11741415B2 (en) | System and method for providing a user interface for KPI customization in an analytic applications environment | |
| CN111625548A (en) | Query method, system, device and computer readable medium | |
| US11971909B2 (en) | Data processing system with manipulation of logical dataset groups | |
| US9411836B2 (en) | Facilitating consistency between a glossary and a repository | |
| US8612190B2 (en) | Derived simulations for planning systems | |
| US11803428B2 (en) | Feature based application programming interface federation | |
| US20240143808A1 (en) | Access controls for modelled content using namespaces | |
| Leonard et al. | Metadata Automation | |
| Cinar et al. | Storing Data |
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 |