CN109388619B - Shared data system and shared data method - Google Patents
Shared data system and shared data method Download PDFInfo
- Publication number
- CN109388619B CN109388619B CN201710684466.1A CN201710684466A CN109388619B CN 109388619 B CN109388619 B CN 109388619B CN 201710684466 A CN201710684466 A CN 201710684466A CN 109388619 B CN109388619 B CN 109388619B
- Authority
- CN
- China
- Prior art keywords
- data
- variable
- name
- shared data
- relationship
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000013500 data storage Methods 0.000 claims abstract description 50
- 238000004364 calculation method Methods 0.000 claims abstract description 10
- 238000013515 script Methods 0.000 claims description 13
- 239000000284 extract Substances 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 10
- 230000014509 gene expression Effects 0.000 description 8
- 238000011161 development Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000011423 initialization method Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A data sharing system and a data sharing method are provided, wherein the data sharing system comprises a data storage device and an application server. The data storage device is used for storing a database. The application server comprises a relation module, a variable module, an analyzer, an interpreter and a shared data builder. The relation module relates at least one attribute of a current entity to at least one attribute or constant of another entity according to a relation name, and extracts the content of at least one current attribute of the current entity and the content of at least one other attribute of another entity from the database. The variable module is used for obtaining variable data from the database according to a variable name, wherein the variable data comprises at least one parameter and is operated to obtain a calculation result. Thereby achieving the effect of reducing the difficulty and complexity of application program development.
Description
Technical Field
The present invention relates to a data sharing system and a data sharing method, and more particularly, to a data sharing system and a data sharing method related to data access logic.
Background
In different functional modules of a software product, when accessing data or accessing a database of a remote storage device, data to be searched by a user usually has the same or similar logic, for example: in both the sales order and the quotation, basic information of the customer is acquired. Traditionally, the reloading is often handled in a targeted manner, for example, in a sales order module, the number and name of a customer need to be obtained according to a customer code (ID), and in a quotation, quotation information needs to be obtained according to the customer and a salesman ID, and in some use situations, a credit line may need to be obtained according to the customer ID.
However, as the services supported by the software product are expanded, the auxiliary functions in the software product may be expanded, and if the software product is developed by the conventional method, the stability is poor, which results in higher maintenance cost.
Disclosure of Invention
In view of the technical problems in the prior art, an object of the present invention is to provide a data sharing system and a data sharing method, which can simplify the development of an application program, reduce the difficulty and complexity of the development of the application program, and reduce the maintenance cost.
To achieve the above objective, the present invention provides a shared data system, which comprises a data storage device and an application server. The data storage device is used for storing a database. The application server comprises a relation module, a variable module, an analyzer, an interpreter and a shared data builder. The relation module relates at least one attribute of a current entity to at least one attribute or at least one constant of another entity according to a relation name, and extracts the content of at least one current attribute of the current entity and the content of at least one other attribute of another entity from the database. Wherein a relationship data comprises at least one current attribute of a current entity and at least one other attribute of another entity. The variable module is used for obtaining variable data from the database according to a variable name, wherein the variable data comprises at least one parameter and is operated to obtain a calculation result. Wherein a variable data comprises at least one parameter and a calculation result. The analyzer is used for analyzing a plurality of shared data used in a script. The interpreter is used for executing a specific interpretation function and a database query function according to a first request generated by the relation module and a second request generated by the variable module, and returning a result set; wherein the result set includes a data structure and common data required for subsequent expansion of the current entity. The shared data builder expands the current entity according to the corresponding relation data and the variable data of the shared data.
In one embodiment, the shared data is stored in a container storage space, and the shared data builder is further configured to release the shared data when the container storage space is closed, so as to manage a life cycle of the shared data.
In an embodiment, the shared data builder is further configured to store the relationship data in a relationship data storage area, and store the data corresponding to the variable data in a variable data storage area.
In one embodiment, the application server includes a relationship data storage area and a variable data storage area.
In one embodiment, the shared data builder comprises a container storage space, and the shared data stored in the container storage space comprises a client number, a client name and a credit limit; wherein, a sales order and a quotation stored in the container storage space respectively use the customer number, the customer name and the credit line.
To achieve the above object, the present invention further provides a method for sharing data, comprising: a relation module is used for connecting at least one current attribute of a current entity to at least one other attribute of another entity according to a relation name, and the content of the at least one current attribute of the current entity and the content of the at least one other attribute of the another entity are taken out from a database; wherein a relationship data comprises at least one current attribute of a current entity and at least one other attribute of another entity; obtaining variable data corresponding to the current entity from a database by a variable module according to a variable name, wherein the variable data comprises at least one parameter and is operated to obtain a calculation result; analyzing, by an analyzer, a plurality of shared data used in a script; executing a specific interpretation function and a database query function by an interpreter according to a first request generated by the relation module and a second request generated by the variable module, and returning a result set; wherein, the result set comprises a data structure and common data needed by the subsequent expansion of the current entity; and expanding the current entity by a shared data builder according to the corresponding relation data and variable data of the shared data.
In one embodiment, the shared data is stored in a container storage space, and the shared data builder is further configured to release the shared data when the container storage space is closed, so as to manage a life cycle of the shared data.
In one embodiment, the shared data builder is further configured to store the relationship data in a relationship data storage area, and store the variable data in a variable data storage area.
In one embodiment, the application server includes a relationship data storage area and a variable data storage area.
In one embodiment, the shared data builder comprises a container storage space, and the shared data stored in the container storage space comprises a client number, a client name and a credit limit; wherein, a sales order and a quotation stored in the container storage space respectively use the customer number, the customer name and the credit line.
In summary, the data sharing system and the data sharing method of the present invention can simplify the development of the application program by the function specifications of the consistent data access, the relationship module and the variable module, reduce the maintenance cost, improve the system efficiency, and reduce the difficulty and complexity of the development of the application program by the simple and practical data expiration mechanism.
The invention is described in detail below with reference to the drawings and specific examples, but the invention is not limited thereto.
Drawings
FIG. 1 is a block diagram of a shared data system according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a data setting interface according to an embodiment of the disclosure;
FIG. 3 is a diagram illustrating a relationship name field according to an embodiment of the present disclosure;
FIG. 4 is a diagram illustrating a variable name field according to an embodiment of the present disclosure;
FIG. 5 is a diagram illustrating an extended current entity according to an embodiment of the present disclosure;
FIG. 6 is a flowchart illustrating a method for initializing shared data according to an embodiment of the present disclosure; and
fig. 7 is a flowchart illustrating a method for sharing data according to an embodiment of the present disclosure.
Wherein, reference numeral 100: shared data system
10: data storage device
20: application server
30: client device
L1, L2: communication connection
22: relationship module
24: variable module
26: analyzer
27: interpreter
28: shared data builder
DB: database with a plurality of databases
200: data set interface
RT, LT: form sheet
201 to 204, 211 to 214, 230, 233: column position
220. 231: push button
A1, a2, B1, B2: data sheet
EN: current entity
ATS: attribute collection
KEY: key-value field
CID: customer ID field
RLC: name of relationship field
CID: customer ID field
NM: customer name field
ADDR: customer address field
VLX, VLG: variable name field
P1, P2: method parameter field
RST: result field
ATS: attribute collection
V1: relational data storage area
V2: variable data storage area
610-660, 710-790: step (ii) of
CL: client device
SR: application server
Detailed Description
The spirit of the present disclosure will be apparent from the accompanying drawings and detailed description, and any person skilled in the art who knows or who can comprehend the teachings of the present disclosure may make changes and modifications without departing from the spirit and scope of the present disclosure.
As used herein, "electrically connected" means that two or more elements are in direct physical or electrical contact with each other or in indirect physical or electrical contact with each other, and "electrically connected" means that two or more elements are in mutual operation or action.
As used herein, the terms "comprising," "including," "having," "containing," and the like are intended to be open-ended terms that mean including, but not limited to.
As used herein, "and/or" includes any and all combinations of the stated items.
As used herein, the term (terms), unless otherwise indicated, shall generally have the ordinary meaning as commonly understood by one of ordinary skill in the art, in the context of this disclosure, and in the context of a particular application. Certain terms used to describe the present disclosure will be discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in describing the present disclosure.
Referring to fig. 1, fig. 1 is a block diagram of a data sharing system 100 according to an embodiment of the present disclosure. In one embodiment, the shared data system 100 includes a data storage device 10 and an application server 20. Application server 20 is communicatively coupled to data storage device 10. In the present embodiment, the application server 20 includes a relationship module 22, a variable module 24, an analyzer 26, and a shared data builder 28. In one embodiment, the data storage device 10 can be implemented by a hard disk, a memory or a flash drive; an application server 20 may be implemented by a computer, a server, or other electronic devices with computing and storage capabilities; the relationship module 22, the variable module 24, the analyzer 26, and the shared data builder 28 may be implemented by an integrated circuit such as a micro controller (mcu), a microprocessor (microprocessor), a digital signal processor (digital signal processor), an Application Specific Integrated Circuit (ASIC), or a logic circuit.
In one embodiment, the data storage device 10 is used for storing a database DB. The shared data system 100 further includes a client device 30, such as a computer, a server, a mobile device or other electronic device with computing capability, the client device 30 can establish a communication link L1 with the application server 20 through a wired or wireless communication manner, and the client device 30 can transmit a request command (for example, generating a manufacturer's trial result report) to the application server 20 through the communication link L1, and the application server 20 obtains related data from the database DB in the data storage device 10 according to the request command. In one embodiment, the data storage device 10 may establish the communication link L2 with the application server 20 through a wired or wireless communication method. In one embodiment, the data storage device 10 may be built in the application server 20.
In one embodiment, an Entity is treated as a table in the relational database, and for an Entity (Entity), it may contain a plurality of attributes (attributes) describing the Entity. Referring to fig. 2, fig. 2 is a schematic diagram of a data setting interface 200 according to an embodiment of the disclosure. As shown in FIG. 2, the fields 201-204 in the left form LT form a hierarchical menu, when the field 204 is selected, the right form RT displays the editable attribute fields 211-214 corresponding to the field 204, and the editable attribute fields 211-214 can be used to add or modify the attributes corresponding to the entities (e.g. the entity described by the content in the field 214 is the content of the field 204), so that, by means of the data setting interface 200, according to the filling rule of each field, each relationship or variable can be named, i.e. a relationship name and a variable name are generated, so that the relationships or variables can be accessed or searched in other functional modules according to the name, and in addition, by clicking the button 220, other associated entities can be selected, or clicking the button 231 in the field 230 can be used to add the description between the attributes or between the entities (as shown in the field 233), and the description can be the conditional expression (e.g.' join "select" syntax) that allows one or more definitions (e.g., in Extensible Markup Language (XML) format) to be set up for subsequent loading or reading of the shared data system 100 during execution.
In one embodiment, through the configuration of the data configuration interface 200, the relationship module 22 is configured to associate at least one attribute of a current entity with at least one attribute or at least one constant of another entity according to a relationship name, and retrieve the content of at least one current attribute of the current entity and the content of at least one other attribute of another entity from the database DB. Wherein, a relation data includes at least one current attribute of the current entity and at least one other attribute of another entity.
In one embodiment, the relationship module 22 is configured to associate at least one attribute or at least one constant of another entity with at least one attribute of the current entity, and so on, and ultimately associate the entity with the data to be accessed.
Referring to fig. 3, fig. 3 is a schematic diagram of a relationship name field according to an embodiment of the present disclosure. The data table a1 in fig. 3 includes a KEY field KEY, a client ID field CID, and a relationship field RLC, and when a code or an expression (expression) attempts to access data through the content in the relationship field RLC, the shared data system 100 acquires the data in the data table B1 according to a predetermined relationship (i.e., according to the relationship of the client ID field CID).
In one embodiment, the variable module 24 is configured to obtain variable data from the database DB according to a variable name, where the variable data includes at least one parameter, and perform an operation to obtain a calculation result. In one embodiment, the variable data may include at least one parameter and a calculation result.
In one embodiment, the variable module 24 is a package for remote service method or attribute calls, and the variable module 24 can handle complex business logic, such as performing data sorting, re-calculation, and the like.
Referring to fig. 4, fig. 4 is a schematic diagram illustrating a variable name field according to an embodiment of the present disclosure. The data table a2 of fig. 4 includes a KEY field KEY, a customer ID field CID, and a variable name field VLX, wherein the variable name can be linked to a predetermined data table B2, and the method parameter fields P1 and P2 in the data table B2 can be substituted into a method, such as: the substitution of the contents of the method parameter fields P1, P2 into the method of querying the number of products sold accumulates the total number of products F1 sold at the respective points of sale in Shanghai (Shanghai) to 100, thereby obtaining the value of the result field RST (for example, to 100).
In one embodiment, the analyzer 26 is used to analyze a plurality of shared data used in a script. Upon initialization of the shared data system 100, the analyzer 26 automatically analyzes shared data used in different scripts or program code in the function. For example, the script content is: since a downstream manufacturer wants to change the upstream shipping factory, it needs to obtain the number of the new upstream shipping factory.
In one embodiment, when the script applies to a sales order and a quotation, the analyzer 26 treats these data as shared data because the sales order and the quotation both apply data of a customer number, a customer name, and a credit line. Generally, the script needs to be interpreted and compiled by the shared data system 100 before subsequent query and/or shared data construction steps can be performed.
In one embodiment, the shared data builder 28 comprises a container storage space (which may be a logical storage space or a physical hard disk space) that stores multiple shared data items, and different functions in the same container storage space can share data items, for example, the shared data items stored in the container storage space include a client number, a client name, and a credit limit. Wherein, a sales order and a quotation stored in the container storage space respectively use the customer number, the customer name and the credit line. Accordingly, the shared data builder 28 may analyze the results of the multiple shared data used in the script based on the analyzer 26 to store the actual shared data and other related data, and extend the structure of the current entity using the relationship name and the variable name to associate the current entity with the actual data storage (e.g., the location of the entity where the data is stored in the storage device 10 or other physical storage device used to store the data) and maintain the independence of the data storage.
In one embodiment, the shared data is stored in the container storage space, and when the container storage space is closed, the shared data builder 28 is further configured to release the shared data from the container storage space (or delete the shared data in the container storage space), so as to manage the life cycle of the shared data.
In one embodiment, when the dependency (e.g., the associated field) of the relationship name or the variable name is changed, the value of the result field RST is also updated or adjusted accordingly. For example, if the field 204 depends on the client ID field CID of the current entity, when the content of the client ID field CID changes, the shared data will re-initiate the request to obtain new data.
By the method, the data validity processing mode is simplified, and the problems of usability and instantaneity are balanced.
In one embodiment, the shared data builder 28 is configured to expand the current entity according to the relationship data and the variable data corresponding to the shared data.
In one embodiment, the application server 20 further includes a relationship data storage V1 and a variable data storage V2, and the shared data builder 28 is further configured to store the relationship data in the relationship data storage V1 and store the data corresponding to the variable data in the variable data storage V2. In one embodiment, the relationship data storage area V1 may store a plurality of relationship data, but the relationship data only includes fields that need to be used, for example, 50 fields in the database DB, if only the client name and address data need to be obtained, the relationship data storage area V1 may not store all 50 fields, but only necessary fields such as: customer ID (used for association), customer name, and customer address field. In some examples, the application server 20 constructs the storage field only when the corresponding data is needed, thereby reducing the overhead of system storage space.
Referring to fig. 5, fig. 5 is a schematic diagram illustrating an extended current entity according to an embodiment of the present disclosure. In fig. 5, the attribute set ATS of the current entity EN includes a KEY field KEY, a relationship field RLC, and a variable name field VLG (e.g., the function of the variable name field is to calculate the tax of the customer), the current entity EN can be defined by the attribute set ATS, and the KEY field KEY in the attribute set ATS can be used to search the current entity EN.
In fig. 5, the relationship name field RLC is associated with the relationship data storage V1, the relationship data storage V1 includes the customer ID field CID, the customer name field NM, and the customer address field ADDR, the variable name field VLG is associated with the variable data storage V2, and the variable data storage V2 includes the method parameter fields P1, P2, and the result field RST. Therefore, when a user or a system automatically wants to expand the current entity EN, the current entity EN can be adjusted or expanded by adjusting the contents of the fields in the relationship data storage V1 and/or the variable data storage V2.
Referring to fig. 6, fig. 6 is a flowchart illustrating a shared data initialization method according to an embodiment of the present disclosure. In step 610, the container storage space is initialized, for example, the contents of the container storage space are emptied, and in step 620, script expressions are registered, which in some examples include expressions that are a combination of numbers, operands, numbers grouped by numbers (e.g., brackets), variables, and the like, in a meaningful permutation that allows values to be obtained. In step 630, the expression is analyzed by an analyzer to interpret the content of the script and then compiled, in step 640, a container storage space object is constructed, some fields that may be needed are set, the shared data is stored in the constructed container storage space, in step 650, a shared data cleaning callback is registered, part of the shared data that is not needed is cleaned to adjust and save the container storage space, in step 660, a storage file is appended to the current entity, and the current entity is expanded according to the relationship data and the variable data corresponding to the shared data.
Referring to fig. 7, fig. 7 is a flowchart illustrating a method for sharing data by an application according to an embodiment of the present disclosure. In FIG. 7, steps 710, 720, 730, 780, and 790 are performed by the client device CL (the steps can also be performed by the application server SR), and steps 740-770 are performed by the application server SR. In one embodiment, steps 710, 720, 730, 780, 790 may be performed on the application server SR, for example: when a document is stored, the stored business logic is carried out in the application server SR. In other words, steps 710, 720, 730, 780, 790 may be performed at the client device CL or the application server SR. In step 710, the expression is executed, and in step 720, the client device CL determines whether to retrieve data (e.g., data required by a portion of the expression has been changed), if so, step 730 is performed, and if not, step 790 is performed. In step 730, the client device CL generates a request object, i.e. informs the application server SR of what data is needed, in step 740, the application server SR parses the request object and obtains the corresponding interpreter 27, thereby interpreting and compiling the content of the script, in some embodiments, the interpreter 27 is configured to execute a specific interpretation function (e.g. performing semantic analysis, transliteration or compilation on the first request and/or the second request) and a database query function according to a first request generated by the relation module 22 and a second request generated by the variable module 24, and returns a result set; wherein, the result set comprises a data structure and common data needed by the subsequent expansion of the current entity EN; in step 750, the interpreter 27 merges the request objects, regarding the request objects required by various functions as shared data, and in step 760, the application server SR generates a query, thereby inputting a search command (query) to the database DB, and in some examples, the application server SR generates a query after sorting and optimizing the shared data, and in step 770, the application server SR merges and transmits the query result to the client device CL. In step 780, the client device CL merges the received query result with known data (e.g., local data existing in the client device CL, which is not required to be queried for obtaining). In step 790, the client device CL obtains the complete query result.
In summary, in order to solve the performance problem of remote access such as cross-network transmission, the system determines whether to merge and compress the request sent to the interpreter according to whether the initiator is cross-remote, so as to balance the performance and overhead. Further, before the request object is generated, it is preferably checked whether the relationship module has a relationship at runtime (e.g., the field associated with the relationship is null) and whether the PreCondition/ValidateExpre of the variable module has been satisfied. If not, the request object is not generated, thereby further reducing unnecessary performance overhead. To increase flexibility, these decisions can be switched by making flexible configurations. In addition, when the association relation in the relation module is found to be invalid (for example, the field is empty), no request will be generated, and on the other hand, when the variable module, in order to solve the instantaneity of the data, the invention can specify whether to acquire the latest data each time in a configuration mode, even if the instant data is acquired, in a batch of operations, such as 1000 order list, the number and name of ITEM number (ITEM) and whether to enable the consultation of stock position management, etc., the request can be sent in the whole batch, that is, the remote request only needs to be sent once, and does not need to be requested one by one. In addition, if the variable module 24 supports batch processing functions (e.g., batch processing flags are made, or incoming and outgoing methods are a set), the batch methods are preferably used during execution by the interpreter 27.
To simplify development, for the results returned by the relationship, a default value for the data type of the request field is returned by default if no matching data is found. For example, when parameter a is requested (in some examples, parameter a may actually be named "activeobject. rl1.rl2. Price" in the program), parameter field B is returned by default if there is no matching data (in some examples, parameter field B may actually be named as a default value of "Price" in the program), and the returned value is 0 assuming that this field is a value type (decimal). For the value returned by the variable, if there is no matching object or the calculation result is empty, the specific object returned at this time may also be defined by applying an Attribute (Attribute) to the method (the method is not limited thereto).
Therefore, the invention can simplify the development of the application program by the function specification of the consistent data access, the relation module and the variable module, reduce the maintenance cost, improve the system efficiency and reduce the difficulty and the complexity of the development of the application program by a simple and practical data expiration mechanism.
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
Claims (6)
1. A shared data system, comprising:
a data storage device for storing a database; and
an application server communicatively coupled to the data storage device, the application server comprising:
a data setting interface for setting a relationship name and a variable name;
a relation module, which is used to connect at least one attribute of a current entity to at least one attribute or at least one constant of another entity according to the relation name, and to take out the content of at least one current attribute of the current entity and the content of at least one other attribute of the another entity from the database; wherein a relationship data comprises the at least one current attribute of the current entity and the at least one other attribute of the other entity;
a variable module for obtaining a variable data from the database according to the variable name, wherein the variable data comprises at least one parameter and is operated to obtain a calculation result;
an analyzer for analyzing a plurality of shared data used in a script;
the interpreter is used for executing a specific interpretation function and a database query function according to a first request generated by the relation module and a second request generated by the variable module and returning a result set; wherein the result set comprises a data structure and common data required for subsequent expansion of the current entity; and
a shared data builder for expanding the current entity according to the relationship data and the variable data corresponding to the shared data,
the shared data builder is further configured to store the relationship data in a relationship data storage area, store data corresponding to the variable data in a variable data storage area, associate the relationship name with the relationship data storage area, associate the variable name with the variable data storage area, and expand the current entity by adjusting the content of the field in the relationship data storage area and/or the variable data storage area.
2. The system of claim 1, wherein the shared data is stored in a container storage space, and the shared data builder is further configured to release the shared data when the container storage space is closed, so as to manage a life cycle of the shared data.
3. The system of claim 1, wherein the shared data builder comprises a container storage space, the shared data stored in the container storage space comprises a client number, a client name, and a credit limit;
wherein, a sales order and a quotation stored in the container storage space respectively use the customer number, the customer name and the credit line.
4. A method for sharing data, comprising:
setting a relationship name and a variable name by a data setting interface;
using a relation module to connect at least one current attribute of a current entity to at least one other attribute of another entity according to the relation name, and taking out the content of the at least one current attribute of the current entity and the content of the at least one other attribute of the another entity from a database; wherein a relationship data comprises the at least one current attribute of the current entity and the at least one other attribute of the other entity;
obtaining variable data from the database by a variable module according to the variable name, wherein the variable data comprises at least one parameter and is operated to obtain a calculation result;
analyzing, by an analyzer, a plurality of shared data used in a script;
executing a specific interpretation function and a database query function by an interpreter according to a first request generated by the relation module and a second request generated by the variable module, and returning a result set; wherein the result set comprises a data structure and common data required for subsequent expansion of the current entity; and
expanding the current entity by a shared data builder according to the relationship data and the variable data corresponding to the shared data,
the shared data builder is further configured to store the relationship data in a relationship data storage area, store data corresponding to the variable data in a variable data storage area, associate the relationship name with the relationship data storage area, associate the variable name with the variable data storage area, and expand the current entity by adjusting the content of the field in the relationship data storage area and/or the variable data storage area.
5. The method of claim 4, wherein the shared data is stored in a container storage space, and the shared data builder is further configured to release the shared data when the container storage space is closed, so as to manage a life cycle of the shared data.
6. The method of claim 4, wherein the shared data builder comprises a container storage space, the shared data stored in the container storage space comprises a client number, a client name, and a credit limit; wherein, a sales order and a quotation stored in the container storage space respectively use the customer number, the customer name and the credit line.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710684466.1A CN109388619B (en) | 2017-08-11 | 2017-08-11 | Shared data system and shared data method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710684466.1A CN109388619B (en) | 2017-08-11 | 2017-08-11 | Shared data system and shared data method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109388619A CN109388619A (en) | 2019-02-26 |
| CN109388619B true CN109388619B (en) | 2021-11-02 |
Family
ID=65414528
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710684466.1A Active CN109388619B (en) | 2017-08-11 | 2017-08-11 | Shared data system and shared data method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109388619B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111984336A (en) * | 2020-07-08 | 2020-11-24 | 广东易达电子科技有限公司 | Personalized desktop setting method, device and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1949763A (en) * | 2005-10-11 | 2007-04-18 | 北京航空航天大学 | Shared message server system |
| CN102999522A (en) * | 2011-09-15 | 2013-03-27 | 阿里巴巴集团控股有限公司 | Data storage method and device |
| JP2014186698A (en) * | 2013-03-25 | 2014-10-02 | Hitachi Systems Ltd | Load distribution system, load distribution system data sharing method and load distribution system data sharing program |
| CN106230975A (en) * | 2016-08-31 | 2016-12-14 | 山东众阳软件有限公司 | Based on master index cloud platform across institute's data sharing, Real-Time Sharing method and system |
| CN106470216A (en) * | 2015-08-14 | 2017-03-01 | 江贻芳 | A kind of Content Management System based on information sharing, interaction |
| US9697104B2 (en) * | 2015-12-07 | 2017-07-04 | Sap Se | End-to end tracing and logging |
-
2017
- 2017-08-11 CN CN201710684466.1A patent/CN109388619B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1949763A (en) * | 2005-10-11 | 2007-04-18 | 北京航空航天大学 | Shared message server system |
| CN102999522A (en) * | 2011-09-15 | 2013-03-27 | 阿里巴巴集团控股有限公司 | Data storage method and device |
| JP2014186698A (en) * | 2013-03-25 | 2014-10-02 | Hitachi Systems Ltd | Load distribution system, load distribution system data sharing method and load distribution system data sharing program |
| CN106470216A (en) * | 2015-08-14 | 2017-03-01 | 江贻芳 | A kind of Content Management System based on information sharing, interaction |
| US9697104B2 (en) * | 2015-12-07 | 2017-07-04 | Sap Se | End-to end tracing and logging |
| CN106230975A (en) * | 2016-08-31 | 2016-12-14 | 山东众阳软件有限公司 | Based on master index cloud platform across institute's data sharing, Real-Time Sharing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109388619A (en) | 2019-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220147326A1 (en) | Automated api code generation | |
| CN111209004B (en) | Code conversion method and device | |
| US6738077B1 (en) | Dynamic generation and automated distribution of user interface from database model | |
| US8713048B2 (en) | Query processing with specialized query operators | |
| CN104838377B (en) | It is handled using mapping reduction integration events | |
| US10061749B2 (en) | Systems and methods for contextual vocabularies and customer segmentation | |
| US8219650B2 (en) | Communicating with a status management component in a computer system | |
| US9043750B2 (en) | Automated generation of two-tier mobile applications | |
| US20020069192A1 (en) | Modular distributed mobile data applications | |
| US20160306896A1 (en) | Extending graph traversals with application logic | |
| US20100023952A1 (en) | Platform for data aggregation, communication, rule evaluation, and combinations thereof, using templated auto-generation | |
| US9967370B2 (en) | OData enabled mobile software applications | |
| CN108369591B (en) | System and method for caching and parameterizing IR | |
| CN109766354A (en) | Optimization method, device and the equipment of business datum inquiry | |
| US20180321831A1 (en) | Smart controls for user interface design and implementation | |
| KR20170085097A (en) | Systems and methods for search query rewrites | |
| US9507567B2 (en) | Facilitating use of techniques implemented by external library functions in process definitions of analytical applications | |
| CN111158651A (en) | Method, device and system for constructing artificial intelligence application | |
| CA2538561C (en) | System and method for conversion of web services applications into component based applications for devices | |
| US11237945B2 (en) | Configuration content integration | |
| CN109388619B (en) | Shared data system and shared data method | |
| CN113918602A (en) | Data caching method and device and electronic equipment | |
| TWI699658B (en) | Data sharing system and data sharing method | |
| US20150347573A1 (en) | Information Processing Device and Method Therefor, and Non-Transitory Computer Readable Medium | |
| US20110208746A1 (en) | Systems and methods for message-based distributed computing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20190226 Assignee: Shanghai Dingjie Shuzhi Software Co.,Ltd. Assignor: DIGIWIN SOFTWARE Co.,Ltd. Contract record no.: X2024310000112 Denomination of invention: Shared Data System and Methods Granted publication date: 20211102 License type: Common License Record date: 20240903 |