CN107832349B - Business object management method and information management system - Google Patents
Business object management method and information management system Download PDFInfo
- Publication number
- CN107832349B CN107832349B CN201710983497.7A CN201710983497A CN107832349B CN 107832349 B CN107832349 B CN 107832349B CN 201710983497 A CN201710983497 A CN 201710983497A CN 107832349 B CN107832349 B CN 107832349B
- Authority
- CN
- China
- Prior art keywords
- target
- version
- identifier
- record table
- determining
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a business object management method and an information management system, which are used for separating the storage of object version data and relation set version data, reducing the data storage capacity and further saving the storage space. The method in the embodiment of the application comprises the following steps: when a business object is established or updated, storing object version data of the business object to a first record table, and recording a first operation of storing the object version data on an operation record table according to the time sequence of the operation; and when the incidence relation of the business object is established or updated, storing the relation set version data of the business object to a second record table, and recording a second operation for storing the relation set version data on the operation record table according to the time sequence of the operation.
Description
Technical Field
The present application relates to the field of information management, and in particular, to a method and system for managing a service object.
Background
In the information management system, business objects (also referred to as objects for short) record the data state of the objects in the form of object version data, and the data association state between the objects with specific association relationship (such as composition relationship, reference relationship, etc.) is recorded between different objects in the form of relationship set version data.
Since the number of association relations and the number of objects are in a combined relation (for example, the relation between A, B, C, D is A-B, A-C, A-D, B-C, B-D, C-D), and the kinds of association relations are also various. In the conventional solution, version data of objects such as B, C, D associated with a certain object a is recorded, and when object version data of a certain object B among the objects associated with the certain object a is updated, object version data of all objects such as A, C, D associated with the updated object are also updated and stored again.
The management mode of the object causes the stored relational data to have large quantity and much data redundancy, and consumes a large amount of storage space.
Disclosure of Invention
The embodiment of the application provides a business object management method and an information management system, which are used for separating the storage of object version data and relation set version data, reducing the data storage capacity and further saving the storage space.
The specific technical scheme comprises the following steps:
the embodiment of the application provides a method for managing a business object, which comprises the following steps:
when a business object is established or updated, storing object version data of the business object to a first record table;
recording a first operation on an operation record table according to the time sequence of the operation, wherein the first operation is an operation for saving the object version data;
when the incidence relation of the business object is established or updated, the relation set version data of the business object is stored in a second record table;
and recording a second operation on the operation record table according to the time sequence of the operation, wherein the second operation is the operation of saving the relation set version data.
Preferably, the first record table includes an object identifier and a first version identifier, the object identifier is used for uniquely identifying the business object, and the first version identifier is used for identifying an object version of the business object;
the second record table comprises the object identifier, a second version identifier, a relationship type and an associated object identifier, the second version identifier is used for identifying the relationship set version of the business object, the relationship type is used for identifying the type of the association relationship between the business object and the associated business object, and the associated object identifier is used for uniquely identifying the associated business object.
Preferably, the operation record table includes a time point, an operation object identifier, an operation version identifier and an operation type, and the time point is used for identifying a time sequence of each operation;
when the first operation is carried out, the operation type is an object, and the operation object identification comprises the object identification;
when the second operation is performed, the operation type is a relationship, and the operation object identifier includes the object identifier and the relationship type.
Preferably, the method further comprises:
determining a target business object to be checked;
searching target object version data corresponding to the target business object according to a first preset method;
and/or the presence of a gas in the gas,
and searching target relation set version data corresponding to the target business object or target associated object version data of a target associated business object having a target associated relation with the target business object according to a second preset method.
Preferably, the first preset method includes:
determining an object identifier of the target business object;
determining the target object identifier closest to the time point in the operation record table according to the object identifier;
determining a target first version identification corresponding to the target object identification;
and determining the target object version data in the first record table according to the target first version identification.
Preferably, the second preset method includes:
determining the object identification and the relationship type of the target business object;
determining the target second version identification closest to the time point in the operation record table according to the object identification and the relationship type;
and determining the target relation set version data in the second record table according to the target second version identification.
Preferably, the method further comprises:
determining an associated object identifier corresponding to the target second version identifier in the second record table according to the target second version identifier;
determining a target associated object identifier closest to the time point in the operation record table according to the associated object identifier;
determining a target associated first version identification corresponding to the target associated object identification;
and determining the target associated object version data in the first record table according to the target associated first version identification.
The embodiment of the present application provides an information management system, where the information management system specifically implements a function implemented by the information management system in a management method corresponding to the business object, and the function may be implemented by hardware or by hardware executing a corresponding software program. The hardware and software includes one or more unit modules and/or sub-unit modules corresponding to the above-described functions, and the unit modules and/or sub-unit modules may be software and/or hardware.
An embodiment of the present application provides an information management system, including:
the system comprises a processor, a memory, a bus and an input/output interface, wherein the processor, the memory and the input/output interface are connected through the bus; the memory is stored with a program code, and the program code is used for storing an operation instruction; the processor is configured to execute, when calling the program code in the memory, steps that need to be executed by the information management system in the method for managing a business object according to any of the embodiments of the present application.
Embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the steps of the method for managing business objects in embodiments of the present application.
It should be noted that, in essence, or a part or all or part of the technical solution that contributes to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium and is used for storing computer software instructions for the information management system, and when the instructions are run on a computer, the instructions cause the computer to execute the steps of the method for managing a business object in the embodiment of the present application.
The storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and is not limited herein.
According to the technical scheme, the embodiment of the application has the following advantages:
when a business object is established or updated, storing object version data of the business object to a first record table, and recording a first operation of storing the object version data on an operation record table according to the time sequence of the operation; and when the incidence relation of the business object is established or updated, storing the relation set version data of the business object to a second record table, and recording a second operation for storing the relation set version data on the operation record table according to the time sequence of the operation. In the embodiment of the application, the storage of the object version data and the relation set version data is separated, so that the data storage capacity is reduced, and the storage space is saved.
Drawings
FIG. 1 is a diagram illustrating object version data and relationship set version data of a business object stored in the prior art;
fig. 2 is a schematic diagram of storing object version data and relationship set version data of a business object in an embodiment of the present application;
FIG. 3 is a schematic diagram of an embodiment of a method for managing a business object in an embodiment of the present application;
FIG. 4 is a diagram illustrating an application scenario for updating object version data according to an embodiment of the present application;
FIG. 5 is a diagram illustrating an application scenario for updating the relationship set version data according to an embodiment of the present application;
FIG. 6 is a schematic diagram of another embodiment of a method for managing a business object in an embodiment of the present application;
FIG. 7 is a diagram illustrating an application scenario for finding object version data of a business object according to an embodiment of the present application;
FIG. 8 is an application scenario diagram illustrating the search for relationship set version data of a business object in an embodiment of the present application;
fig. 9 is an application scene diagram of object version data and relationship set version data for searching a business object in the embodiment of the present application;
FIG. 10 is a schematic diagram of an embodiment of an information management system in an embodiment of the present application;
fig. 11 is a diagram of an entity apparatus of an information management system according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a business object management method and an information management system, which are used for separating the storage of object version data and relation set version data, reducing the data storage capacity and further saving the storage space.
In the prior art, an information relationship system stores object version data and relationship set version data as follows: when the object version data of any one of the object B, C, D and the like having an association with the object a is changed, the information management system restores all the object version data having an association again regardless of whether the association is changed or not and regardless of whether the other object version data having an association is updated or not. Especially in version changes (e.g., A parent-B child, modifying the referenced object B), impact analysis is required due to the reference of the relationship (e.g., evaluation is performed on the referenced object A, where not only A but all B referenced objects are), especially inheritance relationship (e.g., A is also referenced by other object C, and the change of B also affects C); the referencing causes the analysis of the changes to become cumbersome and also consumes a lot of runtime and memory space. As shown in FIG. 1, no matter whether the relationship set version of the object A is changed, as long as the object A (e.g., version 1.0) is modified, the updated version of the object A (e.g., version 2.0) needs to store a set of relationship set version data (e.g., from the relationship set version 1.0 to the relationship set version 2.0), and meanwhile, the corresponding object B, C, D … with the association relationship also needs to be saved again for the version of the object which is not updated (e.g., object B, C, D and the like respectively save version 2.0, version 2.1 and version 5.1 … again), and meanwhile, the influence on the object A needs to be analyzed reversely when the objects such as B, C, D … and the like are changed.
In the embodiment of the application, when the version of the business object is changed, only the data of the changed object version of the business object is stored; when the incidence relation of the business object changes, only storing the changed relation set version data of the business object; this eliminates the need to record a set of relationship set version data for each object version of the business object. As shown in fig. 2, when the object a changes the object version to version 1.0 at time point 1, only the object version of the object a is stored; when the object A changes the relation set version to the relation set 2.0 at the time point 2, only the relation set version of the object A is stored; when the object version of the object A is changed to version 2.0 at the time point 3, only the object version of the object A is stored, and so on.
For convenience of understanding, a specific flow in the embodiment of the present application is described below, and referring to fig. 3, an embodiment of a method for managing a business object in the embodiment of the present application includes:
301. storing the object version data of the business object to a first record table;
when a business object is established or updated, storing object version data of the business object to a first record table;
it should be noted that, the first record table in this embodiment of the application refers to a storage unit or a storage module capable of storing version data of a business object, and any software and/or hardware capable of implementing a function of storing object version data of a business object when a business object is created or updated may be used, which is not limited herein.
It should be further noted that the first record table may include an object identifier and a first version identifier, where the object identifier is used to uniquely identify the service object, for example, the object identifier of the service object a is a; the first version identifier is used to identify an object version of the business object, for example, if the object version of the object a is an unmodified version for the first time, the first version identifier may be written as V1.0, or may be written as a1.0, which is not limited herein.
It should be further noted that the first record table may include an object identifier and a first version identifier, and may also include an object name, for example, the object name corresponding to the object a may be a specific "car", or may be an abstract functional concept "brake", and the specific description is not limited herein.
302. Recording the first operation on an operation recording table according to the time sequence of the operation;
after the object version data of the business object is stored in the first record table, the first operation of storing the object version data is recorded on the operation record table according to the time sequence of the operation.
It should be noted that the operation record table may include a time point, an operation object identifier, an operation version identifier, and an operation type, where the time point is used to identify a time sequence of each operation, such as time point 1, time point 2, and time point 3 … shown in fig. 2.
It should be further noted that, when the first operation is performed, the operation type may be an object, and the operation object identifier includes an object identifier. For example: when the object version data is updated for the object a, the operation object identifier is a, if the last time point is time point 4, the time point of the operation is time point 5, and the operation version identifier is the identifier of the updated object version of the object a. It should be noted that, when the first operation is performed, the operation type may also be represented by a symbol (for example, when the first operation is performed, the operation type is represented by a symbol "& 1", and when the second operation is performed, the operation type is represented by a symbol "& 2"), as long as the symbol can be associated with the first operation and can be distinguished from the second operation, and the specific description is not limited herein.
303. Saving the relation set version data of the business object to a second recording table;
when the association relationship of the business object is established or updated, the relationship set version data of the business object is stored in the second record table.
It should be noted that the second record table may include an object identifier, a second version identifier, a relationship type, and an associated object identifier, where the second version identifier is used to identify a relationship set version of the business object, for example, the relationship set version data having a first association, a second association, and a third association with the object a may be respectively identified as V1.0, V2.0, V3.0, etc., or respectively identified as BV1.0, PV2.0, CV3.0, etc., which is not limited herein; the relationship type is used for identifying the type of the association relationship between the service object and the associated service object, such as a BOM relationship, a PBOM relationship, a reference relationship, and the like, and is not limited herein specifically; the associated object identifier is used for uniquely identifying the associated business object.
304. And recording the second operation on the operation recording table according to the time sequence of the operation.
Similarly, after saving the relationship set version data of the business object to the second record table, the second operation of saving the relationship set version data is recorded on the operation record table according to the time sequence of the operation.
It should be noted that, when the second operation is performed, the operation type is a relationship, and the operation object identifier includes an object identifier and a relationship type, for example, when a certain association relationship of the object a is updated, the operation object identifier may be denoted as "a (BOM)", or may be denoted as "BOM (a)", where a is an object identifier in the operation object identifier, and BOM is a relationship type in the operation thank you identifier, and is a BOM relationship, which is not limited herein. It should be noted that, when the second operation is performed, the operation type may also be represented by a symbol, and is not limited herein.
It should be further noted that there is no fixed time sequence between step 301, step 302, step 303, and step 304, and step 301 and step 302 may be executed first, step 303 and step 304 may be executed first, and step 301 and step 303 may also be executed simultaneously, which is not limited herein.
In the embodiment of the application, when a business object is established or updated, object version data of the business object is stored in a first record table, and a first operation for storing the object version data is recorded on an operation record table according to the time sequence of the operation; and when the incidence relation of the business object is established or updated, storing the relation set version data of the business object to a second record table, and recording a second operation for storing the relation set version data on the operation record table according to the time sequence of the operation. In the embodiment of the application, the storage of the object version data and the relation set version data is separated, so that the data storage capacity is reduced, and the storage space is saved.
Two application scenarios of the embodiments of the present application are described below to further enhance understanding of the embodiments of the present application:
as shown in fig. 4, when the object version data of the object a (object id is a, named: car) is to be updated, the object version data of the object a (e.g.: a, V2.0, car) is saved in the first record table, and further the operation record of this time (e.g.: 5 (i.e. time point 5), a, V2.0, object) is saved in the operation record table.
As shown in fig. 5, when the relationship set version data of the object a is to be updated (e.g., the updated relationship is BOM, the business objects having an association with a are B, C, respectively, and labeled as a-B, A-C), the relationship set version data of the object a (e.g., a (BOM), V2.0, B, C) is saved in the second record table, and the relationship operation record (e.g., 2 (i.e., time point 2), a (BOM), V2.0, relationship) is further saved in the operation record table.
In addition, in this embodiment of the present application, target object version data corresponding to the target service object may be further searched according to a first preset method and/or target relationship set version data corresponding to the target service object may be searched according to a second preset method, specifically referring to fig. 6, an embodiment of a service object management method in this embodiment of the present application includes:
601. storing the object version data of the business object to a first record table;
602. recording the first operation on an operation recording table according to the time sequence of the operation;
603. saving the relation set version data of the business object to a second recording table;
604. and recording the second operation on the operation recording table according to the time sequence of the operation.
In the embodiment of the present application, steps 601 to 604 are similar to steps 301 to 304 in the embodiment shown in fig. 3, and detailed description thereof is omitted here.
605. Determining a target business object to be checked;
when the business object needing to be searched is input in the information management system, the information relation system can determine that the business object needing to be searched is the target business object.
606. Searching target object version data corresponding to the target business object according to a first preset method;
after the target business object to be checked is determined, target object version data corresponding to the target business object is searched according to a first preset method.
The first preset method may include determining an object identifier of a target service object, determining a target object identifier and a target first version identifier corresponding to a target service object at a closest time point in an operation record table according to the object identifier, and determining target object version data corresponding to the target service object in the first record table according to the target first version identifier.
As shown in fig. 7, assuming that the object identifier of the target service object to be searched is a, determining a closest a at a time point in the operation record table according to the object identifier, and if the operation on a at the time point 5 is the closest, determining a corresponding to the time point 5 as the target object identifier, and determining that the operation version identifier in the operation record table corresponding to the a at the time point 5 is V2.0, then the corresponding operation version identifier V2.0 is the target first version identifier corresponding to the a at the time point 5; and finally, determining corresponding target object version data in the first record table according to the time point 5, the target object identifier a and the target first version identifier V2.0, wherein the target object version data corresponding to the time point 5, the target object identifier a and the target first version identifier V2.0 is an automobile.
It should be noted that the first preset method may be other than the above method, and is not limited herein.
607. And searching the version data of the target relation set or the version data of the target associated object corresponding to the target business object according to a second preset method.
After the target business object to be checked is determined, target relation set version data corresponding to the target business object or target associated object version data of a target associated business object having a target association relation with the target business object can be searched according to a second preset method.
When the target relationship set version data needs to be searched, the object identifier and the relationship type of the target business object are determined, then the target second version identifier corresponding to the target business object with the closest time point is determined in the operation record table according to the object identifier and the relationship type, and finally the target relationship set version data corresponding to the target business is determined in the second record table according to the target second version identifier; when target associated object version data of a target associated service object having a target association relation with the target service object needs to be searched, an associated object identifier corresponding to the target second version identifier is determined in a second record table according to the obtained target second version identifier, a target associated object identifier closest to a time point and a target associated first version identifier are determined in an operation record table according to the associated object identifier, and finally the target associated object version data is determined in a first record table according to the target associated first version identifier.
As shown in fig. 8, it is assumed that an object identifier of a target service object to be searched is a, and a relationship type is BOM, when version data of a target relationship set needs to be searched, a (BOM) whose time point is closest is determined in an operation record table according to the object identifier, and if an operation on the a (BOM) at the time point 2 is closest, an operation version identifier of a (BOM) in the operation record table corresponding to the time point 5 is determined to be V1.0, and the corresponding operation version identifier V1.0 is a target second version identifier corresponding to the a (BOM) at the time point 2; finally, corresponding target relation set version data, such as target relation version data corresponding to the time point 2, the operation version identification a (bom) and the target second version identification V1.0, is determined in the second record table according to the time point 2, the operation version identification a (bom) and the target second version identification V1.0. When target associated object version data of a target associated business object having a target associated relationship (e.g., a BOM relationship) with a is to be searched, corresponding associated object identifiers are determined to be B, C in a second record table according to the determined time point 2, operation version identifiers a (BOM), and target second version identifiers V1.0, after B, C is determined, target associated object identifiers closest to B, C time points are determined in the operation record table, if the operation on B at the time point n is closest, B corresponding to the time point n is determined to be one of the target associated object identifiers, and if the operation on C at the time point 0 is closest, C corresponding to the time point 0 is determined to be the other target associated object identifier; subsequently, it is determined that the operation version identifier in the operation record table corresponding to B at the time point n is V3.1, then the corresponding operation version identifier V3.1 is the target-associated first version identifier corresponding to B at the time point n, and it is determined that the operation version identifier in the operation record table corresponding to C at the time point 0 is V4.0, then the corresponding operation version identifier V4.0 is the target-associated first version identifier corresponding to C at the time point 0; finally, the target associated object version data of B, C (such as B, V3.1, braking device; C, V4.0, starting device) is determined in the first record table according to the target associated first version identification corresponding to B, C.
It should be noted that the second preset method may be other than the above method, and is not limited herein.
It should be further noted that the first preset method may be combined with the second preset method, and the first preset method is used to search the version data of the relationship set closest to the time point of the version data of the certain object corresponding to the target business object and the version data of the target associated object. As shown in fig. 9, if it is necessary to search the relationship set version data of the BOM relationship closest to the time point of the object version V2.0 corresponding to the object a and the target associated object version data of the associated object, the time point 5 corresponding to the operation version identifier V2.0 of the object a and the time point 2 corresponding to the operation version identifier V1.0 of the object a (BOM) may be found in the operation record table; according to the method already described in fig. 8, it may be determined that the associated object identifiers corresponding to the time point 2, the operation version identifier a (bom), and the target second version identifier V1.0 are B, C in the second record table, respectively; then, with time point 5 as a starting point, reverse time searching for an operation version identifier corresponding to B, C closest to time point 5, and determining that the operation version identifier of B is V3.1 (i.e. the first version identifier associated with the target corresponding to B is V3.1) and the operation version identifier of C is V4.1 (i.e. the first version identifier associated with the target corresponding to C is V4.1) at time point t, respectively; finally, the target associated object version data (such as B, V3.1, brake device; C, V4.1, engine) of B, C is determined in the first record table according to the target associated first version identification corresponding to B, C.
It should be noted that in some embodiments in the present application, one of step 606 and step 607 may not be needed, and step 606 may be omitted, or step 607 may be omitted, and is not limited herein.
In the above, a detailed description is given to a method for managing a service object in an embodiment of the present application, and referring to fig. 10, an embodiment of an information management system in an embodiment of the present application includes:
a first saving unit 1001 configured to save object version data of a business object to a first record table when the business object is created or updated;
a first recording unit 1002 configured to record a first operation, which is an operation of saving the object version data, on the operation record table in chronological order of the operations;
a second saving unit 1003, configured to, when the association relationship of the business object is established or the association relationship is updated, save the relationship set version data of the business object to a second record table;
a second recording unit 1004, configured to record a second operation, which is an operation of saving the relationship set version data, on the operation record table in chronological order of the operation.
Preferably, in some embodiments of the present application, the information management system further includes:
a determining unit 1005, configured to determine a target business object to be checked;
a first searching unit 1006, configured to search, according to a first preset method, target object version data corresponding to the target service object;
and/or the presence of a gas in the gas,
a second searching unit 1007, configured to search, according to a second preset method, target relationship set version data corresponding to the target service object or target associated object version data of a target associated service object having a target associated relationship with the target service object.
Preferably, in some embodiments of the present application, the first lookup unit 1006 is further specifically configured to:
determining the object identification of the target business object;
determining the nearest target object identifier of the time point in the operation record table according to the object identifier;
determining a target first version identification corresponding to the target object identification;
and determining the target object version data in the first record table according to the target first version identification.
Preferably, in some embodiments of the present application, the second finding unit 1007 is further specifically configured to:
determining the object identification and the relationship type of the target business object;
determining the target second version identification closest to the time point in the operation record table according to the object identification and the relationship type;
determining the target relationship set version data in the second record table according to the target second version identification.
Preferably, in some embodiments of the present application, the second searching unit 1007 may be further specifically configured to:
determining an associated object identifier corresponding to the target second version identifier in the second record table according to the target second version identifier;
determining a target associated object identifier closest to the time point in the operation record table according to the associated object identifier;
determining a target associated first version identification corresponding to the target associated object identification;
and determining the target associated object version data in the first record table according to the target associated first version identification.
The specific functions and structures of the information management system in the embodiment corresponding to fig. 10 are used to implement the steps processed by the information management system in the embodiments shown in fig. 3 and fig. 6, and details are not repeated here.
As shown in fig. 11, a schematic diagram of an embodiment of an information management system in an embodiment of the present application specifically includes:
the information handling system may vary widely in configuration or performance and may include one or more Central Processing Units (CPUs) 1122 (e.g., one or more processors) and memory 1132, one or more storage media 1130 (e.g., one or more mass storage devices) for storing applications 1142 or data 1144. Memory 1132 and storage media 1130 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 1130 may include one or more modules (not shown), each of which may include a sequence of instructions operating on the information management system. Further, the central processor 1122 may be provided in communication with the storage medium 1130 to execute a series of instruction operations in the storage medium 1130 on the information management system.
The information management system may also include one or more power supplies 1126, one or more wired or wireless network interfaces 1150, one or more input-output interfaces 1158, and/or one or more operating systems 1141, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in the business object processing method described in fig. 3 and fig. 6 are implemented by the information management system based on the structure shown in fig. 11.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of fig. 3 and 6 of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (12)
1. A method for managing a business object, comprising:
when a business object is established or updated, storing object version data of the business object to a first record table;
recording a first operation on an operation record table according to the time sequence of the operation, wherein the first operation is the operation for storing the object version data, the operation record table comprises time points, operation object identifiers, operation version identifiers and operation types, and the time points are used for identifying the time sequence of each operation;
when the incidence relation of the business object is established or updated, the relation set version data of the business object is stored in a second record table;
recording a second operation on the operation record table according to the time sequence of the operation, wherein the second operation is an operation for saving the relation set version data;
determining a target business object to be checked;
searching target object version data corresponding to the target business object according to a first preset method;
the first preset method comprises the following steps:
determining an object identifier of the target business object;
determining the target object identifier closest to the time point in the operation record table according to the object identifier;
determining a target first version identification corresponding to the target object identification;
and determining the target object version data in the first record table according to the target first version identification.
2. The method of claim 1,
the first record table comprises an object identifier and a first version identifier, wherein the object identifier is used for uniquely identifying the business object, and the first version identifier is used for identifying the object version of the business object;
the second record table comprises the object identifier, a second version identifier, a relationship type and an associated object identifier, the second version identifier is used for identifying the relationship set version of the business object, the relationship type is used for identifying the type of the association relationship between the business object and the associated business object, and the associated object identifier is used for uniquely identifying the associated business object.
3. The method of claim 2,
the operation record table comprises time points, operation object identifiers, operation version identifiers and operation types, wherein the time points are used for identifying the time sequence of each operation;
when the first operation is carried out, the operation type is an object, and the operation object identification comprises the object identification;
when the second operation is performed, the operation type is a relationship, and the operation object identifier includes the object identifier and the relationship type.
4. The method according to any one of claims 1 to 3, further comprising:
and searching target relation set version data corresponding to the target business object or target associated object version data of a target associated business object having a target associated relation with the target business object according to a second preset method.
5. The method according to claim 4, wherein the second preset method comprises:
determining the object identification and the relationship type of the target business object;
determining a target second version identifier closest to the time point in the operation record table according to the object identifier and the relationship type;
and determining the target relation set version data in the second record table according to the target second version identification.
6. The method of claim 5, further comprising:
determining an associated object identifier corresponding to the target second version identifier in the second record table according to the target second version identifier;
determining a target associated object identifier closest to the time point in the operation record table according to the associated object identifier;
determining a target associated first version identification corresponding to the target associated object identification;
and determining the target associated object version data in the first record table according to the target associated first version identification.
7. An information management system characterized by comprising:
the first saving unit is used for saving the object version data of the business object to a first record table when the business object is established or updated;
a first recording unit, configured to record a first operation in a chronological order of the operation on an operation record table, where the first operation is an operation for saving the object version data, the operation record table includes a time point, an operation object identifier, an operation version identifier, and an operation type, and the time point is used to identify a chronological order of each operation;
the second storage unit is used for storing the relation set version data of the business object to a second record table when the incidence relation of the business object is established or updated;
a second recording unit, configured to record a second operation on the operation record table in a time order of the operations, where the second operation is an operation of saving the relationship set version data;
the determining unit is used for determining a target business object to be checked;
the first searching unit is used for searching target object version data corresponding to the target business object according to a first preset method;
the first lookup unit is further specifically configured to:
determining an object identifier of the target business object;
determining the target object identifier closest to the time point in the operation record table according to the object identifier;
determining a target first version identification corresponding to the target object identification;
and determining the target object version data in the first record table according to the target first version identification.
8. The information management system according to claim 7, characterized in that the information management system further comprises:
and the second searching unit is used for searching the target relation set version data corresponding to the target business object or the target associated object version data of the target associated business object having the target associated relation with the target business object according to a second preset method.
9. The information management system according to claim 8, wherein the second search unit is further specifically configured to:
determining the object identification and the relationship type of the target business object;
determining a target second version identifier closest to the time point in the operation record table according to the object identifier and the relationship type;
and determining the target relation set version data in the second record table according to the target second version identification.
10. The information management system according to claim 9, wherein the second search unit is further specifically configured to:
determining an associated object identifier corresponding to the target second version identifier in the second record table according to the target second version identifier;
determining a target associated object identifier closest to the time point in the operation record table according to the associated object identifier;
determining a target associated first version identification corresponding to the target associated object identification;
and determining the target associated object version data in the first record table according to the target associated first version identification.
11. An information management system, comprising:
the system comprises a processor, a memory, a bus and an input/output interface;
the memory has program code stored therein;
the processor, when calling program code in the memory, performs the method of any of claims 1 to 6.
12. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710983497.7A CN107832349B (en) | 2017-10-18 | 2017-10-18 | Business object management method and information management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710983497.7A CN107832349B (en) | 2017-10-18 | 2017-10-18 | Business object management method and information management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107832349A CN107832349A (en) | 2018-03-23 |
| CN107832349B true CN107832349B (en) | 2021-06-22 |
Family
ID=61648696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710983497.7A Active CN107832349B (en) | 2017-10-18 | 2017-10-18 | Business object management method and information management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107832349B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109144980A (en) * | 2018-08-21 | 2019-01-04 | 成都四方伟业软件股份有限公司 | Metadata management method, device and electronic equipment |
| CN111061747B (en) * | 2019-12-11 | 2023-08-29 | 金蝶软件（中国）有限公司 | Service bill data updating method and related equipment |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7970742B2 (en) * | 2005-12-01 | 2011-06-28 | Oracle International Corporation | Techniques for implementing indexes on columns in database tables whose values specify periods of time |
| CN101515234A (en) * | 2009-03-26 | 2009-08-26 | 华亚微电子（上海）有限公司 | Associated data processing method and associated data device |
| CN101937378B (en) * | 2009-07-01 | 2014-04-02 | 联想(北京)有限公司 | Method for carrying out back-up protection on data of storage equipment and computer system |
| CN101944089A (en) * | 2009-07-10 | 2011-01-12 | 北京数码大方科技有限公司 | Date view version management method and device for database |
| US10430298B2 (en) * | 2010-10-28 | 2019-10-01 | Microsoft Technology Licensing, Llc | Versatile in-memory database recovery using logical log records |
| CN105243162B (en) * | 2015-10-30 | 2018-10-30 | 方正国际软件有限公司 | Objectification data model querying method and device based on relational data library storage |
| CN107169003B (en) * | 2017-03-31 | 2020-05-22 | 北京奇艺世纪科技有限公司 | Data association method and device |
-
2017
- 2017-10-18 CN CN201710983497.7A patent/CN107832349B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107832349A (en) | 2018-03-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109559234B (en) | Block chain state data storage method, equipment and storage medium | |
| CN108829610B (en) | Memory management method and device in neural network forward computing process | |
| CN111090628A (en) | Data processing method and device, storage medium and electronic equipment | |
| CN109933617B (en) | Data processing method, data processing device, related equipment and related medium | |
| CN107832349B (en) | Business object management method and information management system | |
| CN114968127B (en) | Object calculation storage system, data processing method, client and storage medium | |
| CN111737564A (en) | Information query method, device, equipment and medium | |
| US20130185536A1 (en) | Hash-based managing of storage identifiers | |
| US10853033B1 (en) | Effectively fusing database tables | |
| CN112528067A (en) | Graph database storage method, graph database reading method, graph database storage device, graph database reading device and graph database reading equipment | |
| CN109033456B (en) | Condition query method and device, electronic equipment and storage medium | |
| CN113190623B (en) | Data processing method, device, server and storage medium | |
| CN114374392A (en) | Data compression storage method and device, terminal equipment and readable storage medium | |
| CN112860412A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN115002187B (en) | Binding relation processing method and related equipment | |
| US10503696B1 (en) | Maintaining stable record identifiers in the presence of updated data records | |
| CN116010345A (en) | Method, device and equipment for realizing table service scheme of flow batch integrated data lake | |
| CN113342813B (en) | Key value data processing method, device, computer equipment and readable storage medium | |
| CN112785214B (en) | Inventory optimizing method, device and storage medium | |
| CN111143006B (en) | Method and device for acquiring command help information | |
| CN112632266B (en) | Data writing method and device, computer equipment and readable storage medium | |
| CN111367750B (en) | Exception handling method, device and equipment thereof | |
| CN110830641A (en) | Address list display method, device and equipment and readable storage medium | |
| CN112181995B (en) | Data processing method, device, equipment and storage medium of data table | |
| CN111414162B (en) | Data processing method, device and equipment thereof |
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 |