JP3857749B2 - Persistent object management unit - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
In the object-oriented software, when the object persistence is realized by a relational database management system (hereinafter referred to as RDBMS), the present invention accesses (retrieves, stores, locks) the RDBMS in units of object groups. , Lock release, etc.), thereby enabling consistency between related persistent objects to be maintained.
[0002]
[Prior art]
A persistent object is not an object that is temporarily created or destroyed, but an object that is permanently managed by a database management system or the like. In conventional persistent object management, for example, RDBMS is directly used to store object data in a database to realize object persistence. However, conventionally, there is no means for fetching data from an RDBMS in an arbitrary object group unit, or storing data in the RDBMS, and there is no means for locking or unlocking an object group unit. Therefore, it is necessary to take out and lock / unlock each related object.
[0003]
[Problems to be solved by the invention]
When an object is retrieved and updated, that is, when data of an object stored in the database is retrieved and updated, the objects associated with the object are also retrieved, stored, locked / unlocked, etc. Otherwise, data consistency among objects cannot be maintained.
[0004]
However, in the conventional method of directly using RDBMS, there is no means for fetching and storing RDBMS data in groups of arbitrary objects, and locking / unlocking of objects in groups. It is difficult to maintain the performance, the burden of development of application programs, etc. is large, and maintenance of the developed program is difficult.
[0005]
The present invention solves the above-described problems and provides a means for enabling access to the RDBMS in units of arbitrary object groups so that consistency between related objects can be easily maintained. For the purpose.
[0006]
[Means for Solving the Problems]
FIG. 1 is an explanatory diagram of the principle of the present invention. In the figure, 10 is an object group management information generating device, 20 is an object group management device, 30 is a relational database management system (RDBMS), and 40 is a relational database.
[0007]
The object / group management information generating apparatus 10 is an apparatus that associates each object with a group including the object and automatically generates data necessary for maintaining the state of the group in the RDBMS 30.
[0008]
The object group management device 20 is a means for collectively retrieving objects from a specified group from the RDBMS 30, a means for automatically retrieving objects within the same group from the RDBMS 30 and locking them to the group of objects. , Means for releasing the lock applied to the group of objects, means for collectively storing the objects of the specified group in the RDBMS 30, and saving an object in the RDBMS 30 automatically collects the objects in the same group to the RDBMS 30 It is a device having means for storing.
[0009]
The RDBMS 30 is a device that manages the relational database 40 and executes input / output with respect to the relational database 40, and is similar to a conventionally used relational database management system.
[0010]
The object group management information generation device 10 and the object group management device 20 can be realized as, for example, object-oriented software (object).
[0011]
The operation of the present invention is as follows.
When an object group is specified, the object group management information generation apparatus 10 receives data (group configuration data) indicating the correspondence between the specified object and the group and data (group status data) indicating the group status (RDBMS 30). Generate automatically within.
[0012]
For example, when an object is extracted at the time of starting an application, at the time of updating an object, at the time of searching, etc., the object group management device 20 is generated by the object group management information generation device 10 when a group of objects to be extracted is designated. Using the group configuration data thus obtained, all objects in the group are searched, and they are collectively extracted from the RDBMS 30.
[0013]
When an object to be extracted is designated, the object group management device 20 first identifies the group to which the object belongs using the group configuration data generated by the object group management information generation device 10, and then identifies the object within the group. Are retrieved from the RDBMS 30 together.
[0014]
When it is desired to lock / unlock access to a group, the object group management device 20 uses the group configuration data generated by the object group management information generation device 10 to lock / unlock the group as a unit. Then, the lock / unlock state of the group state data generated by the object group management information generation device 10 is rewritten to indicate whether the specified group of objects is in a locked state. When a certain group is in a locked state, the object group management device 20 does not accept an update for the group or an object belonging to the group.
[0015]
When a group to be stored is designated, the object group management apparatus 20 stores all objects in the group in the RDBMS 30 using the group configuration data generated by the object group management information generation apparatus 10.
[0016]
When the object to be stored is designated, the object group management device 20 first identifies the group to which the object belongs using the group configuration data generated by the object group management information generation device 10, and then selects the object in the group. All of them are searched and collectively stored in the RDBMS 30.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 2 is a diagram showing a configuration example in an embodiment of the present invention.
In FIG. 2, 10 is an object / group management information generating device, 11 is an object / group configuration data registering unit, 12 is an object ID assigning unit, 13 is an object ID data area generating unit, 14 is a group data generating unit, and 20 is an object. A group management device, 21 is a group extraction unit, 22 is an object group extraction unit, 23 is a group lock setting unit, 24 is a group lock release unit, 25 is a group update unit, 26 is a group lock state check unit, Reference numeral 27 denotes an object group update unit, 30 denotes a relational database management system (RDBMS), 40 denotes a relational database, and 50 denotes an application program or a management user interface.
[0018]
FIG. 3 is a diagram showing a configuration example of the management table in the present embodiment.
3A is a table 60 corresponding to each object stored in the relational database 40, FIG. 3B is an object group configuration table 61 that stores the correspondence between objects and groups, and FIG. The group state table 62 which memorize | stores the state of a group is shown.
[0019]
[1] When registering a group of objects
When one or more objects specified as a group are input from the application program or the management user interface 50, the object group configuration data registration unit 11 checks whether or not the input object has an ID. If the user does not have an ID, the object is input to the object ID assigning unit 12.
[0020]
The object ID assigning unit 12 assigns a new unique ID value to the input object, and updates the value of the object_id column of the table 60 corresponding to the object.
[0021]
When there is no object_id column in the input object table 60, the object group configuration data registration unit 11 inputs the object name into the object ID data area generation unit 13 and newly adds the object_id column to the corresponding table 60. Add to This processing takes into consideration that the present invention can be used even when an object of an existing program is used.
[0022]
If object_id is assigned to the input object, the object / group configuration data registration unit 11 inputs the object to the group data generation unit 14.
[0023]
The group data generation unit 14 assigns a new group ID value and adds a new row having the ID of the group and the ID of the object belonging to the group to the object group configuration table 61. In addition, a row having a new group ID is added to the group status table 62.
[0024]
FIG. 3 shows an example in which three objects are registered as one group. The object_id column of the tables 60A, 60B, and 60C corresponding to each object shown in FIG. 1, 2, and 3 are assigned as ID values.
[0025]
In the object group configuration table 61, as shown in FIG. 3B, the ID value of the new group is 1 in the group_id column, and the ID values 1, 2, 3 of the objects constituting the group are displayed in the object_id column. A line consisting of
[0026]
Further, in the group status table 62 in FIG. 3C, the status of the newly registered group is set in the status column. In this status column, for example, “locked” is set when the group (group_id = 1) is locked, and “unlocked” is set when the group is not locked.
[0027]
FIG. 4 shows a flow of processing for generating data of a new object group.
In step S1, one or more objects designated as a group are input.
[0028]
In step S2, the input objects are examined in order.
In step S3, it is determined whether the input object has an ID value. If the object has an ID value, the process proceeds to step S7. If the object does not have an ID value, the process proceeds to step S4.
[0029]
In step S4, it is determined whether or not the table 60 corresponding to the object has an object_id column. When the table 60 has the object_id column, the process proceeds to step S6. When the table 60 does not have the object_id column, the process of step S5 is performed.
[0030]
In step S5, an object_id column is added to the table 60 corresponding to the object.
In step S6, an ID value is assigned to the object, and the object_id column of the row corresponding to the object is updated with the assigned ID value.
[0031]
In step S7, it is determined whether or not all the objects designated by the group have been examined. When all the objects have been examined, the process proceeds to step S8. When all the objects have not been examined, the process returns to step S2 and similarly. Repeat the process.
[0032]
In step S8, a new group ID value is assigned.
In step S9, a new line is added to the object group configuration table 61 for each group-designated object. The ID value of the new group is stored in the group_id column of the new row, and the ID value of each object is stored in the object_id column.
[0033]
In step S10, a new row in which group_id is the ID value of the new group is added to the group status table 62.
[2] When retrieving all objects by specifying a group
The group ID of the group to be extracted is input to the group extraction unit 21 from the application program or the management user interface 50.
[0034]
The group extraction unit 21 searches the object group configuration table 61 and obtains the ID of the object corresponding to the input group ID. Next, all the tables 60 corresponding to the object are searched, a line matching the object ID is obtained, and the object is generated from the data of this line.
[0035]
FIG. 5 shows a flow of processing for extracting objects collectively by specifying a group.
In step S <b> 11, the group ID value is input to the group extraction unit 21.
[0036]
In step S12, the group extraction unit 21 searches the object group configuration table 61, and obtains the object ID from the line where the value of group_id matches the input ID value.
[0037]
In step S13, all the tables 60 corresponding to each object are searched with the object ID obtained in the process of step S12.
In step S14, an object is generated from the row data obtained as a result of the search.
[0038]
[3] When a certain object is specified and all the objects to which the object belongs are extracted
The ID value of the object to be extracted is input to the object group extraction unit 22 from the application program or the management user interface 50.
[0039]
The object group extraction unit 22 searches the object group configuration table 61 to obtain the group ID corresponding to the object ID, and inputs this value to the group extraction unit 21. The subsequent processing is the same as the processing described in [2].
[0040]
FIG. 6 shows a flow of processing for designating a certain object and extracting all objects in the group to which the object belongs.
In step S 15, the object ID value is input to the object group extraction unit 22.
[0041]
In step S16, the object group retrieval unit 22 searches the object group configuration table 61, and obtains the group ID from the line where the value of object_id matches the input ID value.
[0042]
In step S17, the group ID obtained in step S16 is input to the group extraction unit 21. Thereafter, the group take-out unit 21 performs steps S11 to S14 shown in FIG.
[0043]
[4] Group lock / unlock processing
In the following, for simplicity of explanation, the type of lock is described as one type of access prohibition, but as a lock for a group, for example, multiple levels of lock such as rewrite prohibition and read prohibition may be performed.
[0044]
The ID of the group to be locked is input to the group lock setting unit 23 from the application program or the management user interface 50. The group lock setting unit 23 rewrites the data in the status column of the row corresponding to the group ID in the group state table 62 to locked (locked state).
[0045]
FIG. 7 shows a flow of processing for locking a group.
In step S 21, the group ID value is input to the group lock setting unit 23.
[0046]
In step S22, the group state table 62 is searched, and the value of the status column in the row whose group_id value matches the input ID value is rewritten to locked (locked state).
[0047]
On the other hand, when the group lock is released, the ID of the group to be unlocked is input to the group lock release unit 24 from the application program or the management user interface 50. The group lock release unit 24 rewrites the value of the status column of the row corresponding to the group ID in the group state table 62 to the unlock state.
[0048]
FIG. 8 shows a flow of processing for releasing the group lock.
In step S 23, the group ID value is input to the group lock release unit 24.
[0049]
In step S24, the group state table 62 is searched, and the value of the status column in the row where the value of group_id matches the input ID value is rewritten to the unlocked state.
[0050]
[5] When updating a group of objects by specifying a group
The ID of the group to be updated is input to the group update unit 25 from the application program or the management user interface 50.
[0051]
The group update unit 25 inputs the group ID to the group lock state check unit 26.
The group lock state check unit 26 searches the group state table 62, and if the value in the status column corresponding to the input group ID is in the locked state, issues a message indicating that the update cannot be performed and ends the process. Here, if the value in the status column corresponding to the input group ID is not locked, the object group configuration table 61 is searched to obtain the ID of the object corresponding to the input group ID. Next, the data of all the rows corresponding to this object ID are updated together.
[0052]
FIG. 9 shows a flow of processing for updating a group of objects by specifying a group.
In step S31, the ID value of the group to be updated is input to the group update unit 25.
[0053]
In step S32, the group status table 62 is searched to check whether the group is locked.
In step S33, it is determined whether or not the group is in the locked state. If the group is in the locked state, the process of step S36 is performed. If not in the locked state, the process proceeds to step S34.
[0054]
In step S34, the object group configuration table 61 is searched, and the ID of the object is obtained from the line where the value of group_id matches the input ID value.
[0055]
In step S35, data in all rows corresponding to the object ID obtained in step S34 is updated.
In step S36, a message indicating that updating is not possible is issued.
[0056]
[6] When an object is specified and all objects in the group to which the object belongs are updated together
An ID of an object belonging to the group to be updated is input to the object group updating unit 27 from the application program or the management user interface 50.
[0057]
The object group updating unit 27 searches the object group configuration table 61 to obtain the group ID corresponding to the object ID. This value is input to the group update unit 25. The subsequent processing is the same as the processing described in [5] above.
[0058]
FIG. 10 shows a flow of processing for designating a certain object and updating all the objects in the group to which the object belongs.
In step S 41, the object ID value is input to the object group update unit 27.
[0059]
In step S42, the object group configuration table 61 is searched, and the ID of the group is obtained from the row where the value of object_id matches the input ID value.
[0060]
In step S43, it is determined whether there is a group ID. When there is a group ID, the process of step S44 is performed, and when there is no group ID, the process of step S45 is performed.
[0061]
In step S44, the group ID is input to the group update unit 25. Thereafter, the processing shown in FIG. 9 is performed.
In step S45, only the object with the specified ID is updated.
[0062]
【Example】
Next, as an embodiment of the present invention, an example in which the accommodation reservation business program is realized by object-oriented software will be described.
[0063]
FIG. 11 shows a configuration example of each processing unit expressed in the object-oriented software language in the embodiment.
The object group management information generation apparatus 10 shown in FIG. 2 is realized by an object group management information generation object [object name: OGGenerator (denoted as OGGnr in the figure)] 110. The object group management information generation apparatus 20 This is realized by a group management object [object name: OGMManager (denoted as OGMng in the figure)] 120.
[0064]
Each means of the object group management information generation apparatus 10 shown in FIG. 2 includes an object group configuration data registration unit [int OG Generator :: enter (PObjGroup * pog)] 111 of the OG Generator 110, and an object ID allocation unit [int OG Generator :: assign_oid ()] 112, a group data generation unit [int OGGenerator :: create_group (PObjGroup * pog)] 113, and a group ID assignment unit [int OGGenerator :: assign_gid ()] 114.
[0065]
Similarly, each means of the object group management apparatus 20 of FIG. 2 includes an OGManager 120 group fetching unit [PObjGroup * OGManager :: retrieve_group (int gid)] 121, an object group fetching unit [PObj * OGManager :: retrieve_og ( int oid)] 122, group lock setting unit [int OGManager :: lock_group (int gid, int status)] 123, group lock release unit [void OGManager :: unlock_group (int gid, int key)] 124, group update Part [void OGManager :: update_group (PObjGroup * pog, int k ey)] 125, group lock state check unit [int OGManager :: check_lock_status (int gid, int key)] 126, object group update unit [void OGManager: update_og (Pobj * og, int key)] 127, object generation The instruction unit [PObj * OGManager :: load_obj (int oid, int cid)] 128 is implemented.
[0066]
Here, for example, “enter” in [intOGGenerator :: enter (PObjGroup * pog)] of the object group configuration data registration unit 111 represents an operation name, “int” represents the type of value to be returned, and “OGGenerator ::” The object class to which the operation name belongs, “(PObjGroup * pog)” indicates that the argument of the operation of enter is the variable name * pog (* is a pointer type variable) of the class PObjGroup. The same notation is used for other operations. These notations are the same as notations known by C ++ language or the like well-known as an object-oriented language, and thus detailed description thereof is omitted.
[0067]
FIG. 12 is a diagram illustrating examples of the contents of the persistent object group class (PObjGroup) 151, the persistent object class (PObj) 152, and the persistent object data storage class (PObjDS) 153 of the application program 150 in the embodiment.
[0068]
In the persistent object group class (PObjGroup) 151, $ pseudo_gid_counter: int, group_id: int, state: int, key: int are attribute names, $ find (gid: int): PObjGroup, enter (), store (), lock (), write (), fix_gid (gid: int), get_pobjs (): Set *, get_po (oid: int): PObj, revive_links () are operation names.
[0069]
Further, in the persistent object class (PObj) 152, $ class_id: int, object_id: int, group_id: int, can_I_lock: int, state: int are attribute names, $ create (), store_group (), lock_group (), store_me (), set_all_linkid (), get_pog (): PObjGroup *, get_key (): int is an operation name.
[0070]
In the persistent object data storage class (PObjDS) 153, $ table_name: char *, $ primary_key: char * are attribute names, $ instance (): PObjDS *, load (oid: int): PObj *, insert (po) : PObj *), update (po: PObj *), and delete (po: PObj *) are operation names.
[0071]
The persistent object group class (PObjGroup) 151 and the persistent object class (PObj) 152 are in a “has_a” relationship (indicated by ◇ in the figure). In other words, it means that the persistent object group class (PObjGroup) 151 has a relationship with zero or more persistent object classes (PObj) 152 (indicated by * in the figure).
[0072]
FIG. 13 is a diagram illustrating an example of an application class definition according to the embodiment using an OMT (Unified_Method) notation.
As shown in FIG. 13A, there are classes of “customer”, “accommodation reservation”, “accommodation reservation details”, “room reservation”, and “room type” as subclasses of the persistent object class (PObj) 152. To do. Here, there is one “accommodation reservation” from the viewpoint of “customer” (indicated by 1 in the figure), and there are 0 or more “customers” from the viewpoint of “accommodation reservation” (indicated by * in the figure). It is in. In addition, from the “accommodation reservation”, the “accommodation reservation” has one or more “accommodation reservation details” (indicated by 1 in the figure). There is a relationship.
[0073]
Further, as shown in FIG. 13B, as a subclass of the persistent object data storage class (PObjDS) 153, “customer DS”, “accommodation reservation DS”, “accommodation reservation detail DS”, “room reservation DS”, Each class of “Room Type DS” exists.
[0074]
FIG. 14 is a diagram illustrating an example of an object actually generated in the accommodation reservation business application.
The customer object, the room reservation object, the room reservation detail object, the room reservation object, and the room type object shown in FIG. 14 constitute one group that is simultaneously extracted from the RDBMS for use in the room reservation business program. The customer object, the room reservation object, the room reservation detail object, and the room reservation object are objects to be locked because it is necessary to maintain data consistency when updating.
[0075]
15 and 16 are diagrams illustrating examples of management tables in the embodiment. 15A shows an example of an object / group configuration table 161, FIG. 15B shows an example of a group status table 162, and FIG. 15C shows an example of a link table 163. These tables hold data about the object group structure and group status. FIG. 16 is an example of tables 170 to 174 corresponding to each object. FIG. 16A shows a customer object table 170, FIG. 16B shows an accommodation reservation object table 171, and FIG. The room reservation object table 172 and FIG. 16D are the room reservation object table 173, and FIG. 16E is the room type object table 174.
[0076]
17 to 23 are diagrams illustrating an operation flow in the embodiment.
FIG. 17 is a diagram showing an operation flow when generating data of a new object group.
[0077]
11 is sent to the object group management information generation object OGGenerator 110 shown in FIG. 11, and the object group configuration data registration unit 111 operates by this, and the customer (customer) , Reservation (accommodation reservation), Rsv_for_night (accommodation reservation details), Rsv_for_room (room reservation), and Room_type (room reservation) objects are input (step S51).
[0078]
The object group configuration data registration unit 111 sequentially checks these input objects (step S52), and determines whether each object has an ID value (step S53). Here, when the object does not have an ID value, the object ID assignment unit 112 is activated by the instruction of “int OGGenerator :: assign_oid ()”, and the ID value is assigned to the object (step S54).
[0079]
After the same processing is performed for each object (step S55), the group ID assigning unit 114 is operated according to an instruction “int OGGenerator :: assign_gid ()”, and an ID value of a new group is assigned (step S56).
[0080]
Next, in response to an instruction “int OGGenerator :: create_group (PObjGroup * pog)”, the group data generation unit 113 is operated, and the ID value of each new group is stored in the object group configuration table 161 in combination with the ID value of each object. (Step S57). Also, a new row that is the ID value of the new group is added to the group status table 162 (step S58).
[0081]
FIG. 18 is a diagram showing a flow of operations when a group is specified and objects are taken out collectively.
An instruction of an operation retrieve_group using the group ID value as an argument is sent to the object / group management object OGManager 120 shown in FIG. 11, and the group fetching unit 121 operates thereby (step S61).
[0082]
The group extraction unit 121 searches the object group configuration table 161, and obtains the object ID (object_id) and class ID (class_id) from the line whose group_id value matches the input ID value (step S62). ). Further, the object / group configuration table 161 and the group state table 162 are referred to, and the lock value of the extracted row is checked (steps S63 and S64).
[0083]
If there is an object whose lock belongs to another group and is readlocked, a message indicating that the object cannot be extracted is issued (step S67), and the process is terminated.
[0084]
If the lock is not applied, the object generation instruction unit 128 is operated according to the instruction “PObj * OGManager :: load_obj (int oid, int cid)”, and the object is processed from the class_id of the object group configuration table 161. The responsible object is specified, and the object is requested to generate an object corresponding to object_id (step S65).
[0085]
As a result, an instruction “PObj * PObjDS :: load (int oid, int cid)” is issued, the object generation unit (not shown) operates, and the object generation unit uses the object ID (object_id), Data necessary for generating an object is extracted from the RDBMS 130, and an object is generated (step S66).
[0086]
FIG. 19 is a diagram showing an operation flow when a certain object is designated and all objects in the group to which the object belongs are extracted.
In response to an instruction “PObj * OGManager :: retrieve_og (int oid)”, an object ID value is input to the object group extraction unit 122 of the object group management object 120 (step S68). The object group extraction unit 122 searches the object group configuration table 161 and obtains the group ID from the line that matches the input ID value (step S69).
[0087]
Next, in response to an instruction “PObjGroup * OGManager :: retrieve_group (int gid)”, the group extraction unit 121 is called and a group ID is input to the group extraction unit 121 (step S70). As a result, all objects in the same group as the designated object are extracted.
[0088]
FIG. 20 is a diagram showing an operation flow when a group is locked.
In response to an instruction “int OGManager :: lock_group (int gid, int status)”, the group lock setting unit 123 operates, and the group ID value and the type of lock (read / write) are input (step S71). .
[0089]
The group lock setting unit 123 searches the group status table 162 and rewrites the value in the status column of the row whose value in the group_id column matches the input ID value to the input lock type (step S72). . Next, a key value for updating the locked data or releasing the lock is passed to the group (step S73).
[0090]
FIG. 21 is a diagram showing a flow of operations when releasing the group lock.
In response to an instruction “void OGManager :: unlock_group (int gid, int key)”, the group lock release unit 124 operates to input the group ID value and the key assigned at the time of lock setting (step S74). The group lock release unit 124 searches the group status table 162, matches the value of the key column in the table with the value of the input key, and the status of the row where the value of group_id matches the input ID value. The column value is rewritten to the unlocked state (steps S75 to S77). If the key values do not match, a message indicating that the lock cannot be released is issued (step S78).
[0091]
FIG. 22 is a diagram showing an operation flow when an object is updated collectively by specifying a group.
In response to an instruction of “void OGManager :: update_group (PObjGroup * pog, int key)”, the group update unit 125 operates and a group to be updated is input (S81). Next, in response to an instruction “int OGManager :: check_lock_status (int gid, int key)”, the group lock state check unit 126 is called to check whether the group can be updated (steps S82 and S83).
[0092]
If it can be updated, the object group configuration table 161 is searched, and the ID and class ID of the row object in which the value of group_id matches the input ID value and the lock is “yes” are obtained ( Step S84). Then, it instructs the object corresponding to the object ID to store data (step S85). In response to an instruction “void PObj :: store_me ()”, data corresponding to the object ID is updated (step S86). If the group to be updated is locked and cannot be updated, a message indicating that the group cannot be updated is output, and the process is terminated (step S87).
[0093]
FIG. 23 is a diagram illustrating an operation flow when an object is specified and all objects in the group to which the object belongs are updated.
In response to an instruction “void OGManager :: update_og (PObj * og, int key)”, the object group update unit 127 operates and an object to be updated is input (step S91). The object group updating unit 127 obtains a group (object) to which the object belongs from the input object (step S92). Next, a group is input to the group update unit 125 according to an instruction of “voidOGManager :: update_group (PObjGroup * pog, int key)”, and the group is updated together (step S93).
[0094]
【The invention's effect】
When updating an object, data consistency among objects cannot be maintained unless data associated with the object is retrieved, stored, locked / unlocked, and the like.
[0095]
According to the present invention, data consistency between related objects can be maintained by taking out, storing, locking / unlocking, etc. RDBMS data in groups of arbitrary objects. In particular, since the mechanism of the present invention can be added as an external function to various object-oriented language processors, the present invention can be easily applied to an existing object-oriented language using a relational database management system. There is an effect that it can be applied.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating the principle of the present invention.
FIG. 2 is a diagram illustrating a configuration example in an embodiment.
FIG. 3 is a diagram illustrating a configuration example of a management table.
FIG. 4 is a diagram showing a flow of processing for generating group data.
FIG. 5 is a diagram showing a flow of processing for collectively retrieving objects by designating a group.
FIG. 6 is a diagram illustrating a flow of processing for designating a certain object and extracting all objects in a group to which the object belongs.
FIG. 7 is a diagram showing a flow of processing for locking a group.
FIG. 8 is a diagram showing a flow of processing for releasing a group lock;
FIG. 9 is a diagram illustrating a flow of processing for updating a group of objects by specifying a group.
FIG. 10 is a diagram showing a flow of processing for designating a certain object and updating all the objects in the group to which the object belongs.
FIG. 11 is a diagram showing a configuration of an example of the present invention.
FIG. 12 is a diagram illustrating an example of a permanent object in the embodiment.
FIG. 13 is a diagram illustrating an example of an application class definition in the embodiment.
FIG. 14 is a diagram illustrating an example of an object in the embodiment.
FIG. 15 is a diagram illustrating an example of a table in the embodiment.
FIG. 16 is a diagram illustrating an example of a table in the embodiment.
FIG. 17 is a diagram illustrating an operation flow when generating group data;
FIG. 18 is a diagram illustrating an operation flow when an object is collectively extracted by designating a group.
FIG. 19 is a diagram illustrating an operation flow when a certain object is designated and all objects in the group to which the object belongs are extracted.
FIG. 20 is a diagram illustrating an operation flow when a group is locked.
FIG. 21 is a diagram showing a flow of an operation when unlocking a group.
FIG. 22 is a diagram illustrating an operation flow when an object is updated collectively by designating a group.
FIG. 23 is a diagram showing an operation flow when an object is specified and all objects in the group to which the object belongs are updated.
[Explanation of symbols]
10 Object group management information generation device
20 Object group management device
30 Relational database management system (RDBMS)
40 relational database

Claims (5)

A persistent object management device for managing persistent objects using a relational database management system,
An object / group management information generating device for generating group management information having group configuration data indicating a correspondence relationship between each object and a group and group status data indicating a group status for managing related objects as a group;
An object group management device that collects related objects from the relational database management system based on the group management information generated by the object group management information generation device ;
The object group management information generating device includes:
An object ID assigning means for assigning a unique ID value for identifying each object as an object ID to a specified object;
Object ID data area generation means for adding a storage area for the object ID in a relational database table corresponding to the specified object;
A unique ID value for identifying an individual group is assigned to a new group as a group ID, and the group configuration data including the correspondence information between the group ID and one or more object IDs, and a set of the group ID and its state information Group data generating means for generating the group state data comprising:
Called when registering a group of objects, and when one or more objects specified by the group are input from the application program or administrative user interface, it is checked whether the input object has an object ID. If no object ID is stored, the object ID is assigned by the object ID assigning means, and there is no storage area for the object ID in the relational database table corresponding to the input object. The ID data area generation means adds the storage area to the table, sets the object ID in the storage area in the table, and sends the group configuration data and the group to the group data generation means. Persistent object management apparatus characterized by comprising an object-group configuration data registration means for generating the up state data. The persistent object management device according to claim 1,
When the object group management device retrieves the objects in the group from the relational database management system, it automatically collects other objects belonging to the same group from the relational database management system based on the group configuration data. A persistent object management device comprising: means. The persistent object management device according to claim 1,
The object group management device comprises means for storing related objects together in a relational database management system based on the group configuration data . The persistent object management device according to claim 1,
When the object group management device stores the objects in the group in the relational database management system, other objects belonging to the same group are automatically collected and stored in the relational database management system based on the group configuration data. A persistent object management device comprising: means for performing the operation. The persistent object management device according to claim 1,
The object group management device comprises means for setting a lock in units of object groups and means for releasing the lock,
Persistent object management device characterized in that consistency information among objects is maintained by storing lock state information for each group as the group state data and prohibiting write or read access to objects in the locked group .

Images