JP2002123414A - Method and device for managing version - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method and a device for managing version by which an object can be registered with an arbitrary version number and the version number is prevented from being mismatched. SOLUTION: When a request accepting part 51 accepts the registering request of an object together with the designation of a version number, an attribute information reference part 52 refers to the version numbers of existent objects, a version determining part 53 performs processing of version number determination so as to keep the consistency of version number, and an attribute information updating part 54 sets the attribute of the object so that the object of the latest version can become only one.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a version management method and apparatus, and more particularly, to a version management method and apparatus for managing a registered object by assigning a consistent version number to the registered object.

[0002]

2. Description of the Related Art Objects such as drawings, documents, and data have the same key attributes (names can be used in addition to those set as keys) and are treated as an object group. Number) is assigned and managed.

[0003] Techniques for managing such version numbers include a "version number management method" described in JP-A-7-152633 and a "version management / configuration management method and apparatus described in JP-A-11-143752. And a computer-readable recording medium on which a version management / configuration management program is recorded.

Generally, as shown in FIG. 8A, version numbers are assigned in order from 1 in the order of registration of objects. Therefore, it was not possible to register a version 5 object in advance and then register a version 1 object.

[0005] For this reason, when a version 3 drawing and a version 4 drawing are simultaneously created by another designer, even if the version 4 drawing is completed first, it must be registered after the version 3 drawing is registered. If this could not be registered. If you want to register version 4 drawings first,
First, as shown in FIG. 8 (b), a dummy drawing is registered as version 3, and subsequently, as shown in FIG. 8 (c), a version 4 drawing is registered. Then, after the drawing of version 3 is completed, by replacing the dummy drawing with the completed drawing, the registration state as shown in FIG. 8D is obtained.

In order to register an object ignoring the order of version numbers, complicated processing is required. For this reason, it has been proposed that an arbitrary version number can be set for an object, but in this case, a plurality of objects having the same version number are registered as shown in FIG. Sometimes
As a result, it may be difficult to manage objects including the latest version.

Here, a flow of the conventional version management will be described. FIG. 9 is a flowchart showing the flow of version management at the time of conventional object registration.

When registering an object, first, a key attribute value of the object to be registered is received (step 501). If the key attribute value is NULL (blank) (YES in step 502), the object is registered without a version number (step 50).
3).

On the other hand, if the key attribute value is not NULL (NO in step 502), the number of the maximum version is determined from the existing objects having the same key attribute value (step 504). Here, if the object of the maximum version does not exist, that is, if there is no existing object having the same key attribute (NO in step 505), the object is registered with the version number “1” (step 506) and registered. The latest version flag attribute indicating that the object is the latest version is set (step 507), and the object registration processing ends.

If the maximum version is found in step 504 and an existing object of the maximum version exists (YES in step 505), the object is registered with a version number of "maximum version + 1" (step 508). ), After resetting the latest version flag attribute set in the existing object of the maximum version (step 509), setting the latest version flag attribute indicating the latest version to the registered object (step 507), The registration processing ends.

FIG. 10 is a flow chart showing a flow of version management when changing a key attribute value of a conventional object.

When changing a key attribute value, first, a new key attribute value to be changed is received (step 601).
Subsequently, the old key attribute value is obtained (step 60).
2).

Here, the acquired old key attribute value is NULL.
If it is not L (NO in step 603) and the target object is the latest version (for the old key attribute value) (YES in step 604), the latest version flag is added to the object of the new version next to the old key attribute value. The attribute is set (step 605), and if the target object is not the latest version (step 604)
NO), the old key attribute value is deleted as it is (step 606). Then, the new key attribute value and the “maximum version + 1” version number are assigned to the target object,
Set the latest version flag attribute (step 60)
7) The key attribute value change processing of the object is terminated.

On the other hand, if the old key attribute value acquired in step 602 is NULL (YES in step 603), the new key attribute value, the version number of “maximum version + 1”, the latest version flag attribute Is set (step 607), and the key attribute value change processing of the object is ended.

[0015]

As described above, in the conventional version management, objects are given version numbers in the order of registration and managed. Therefore, an arbitrary version number is assigned to an object. Could not be attached. In addition, if an object is arbitrarily assigned a version number, inconvenient management of the object occurs, for example, the version number is duplicated or the latest version is unknown.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a version management method and apparatus which can register an object with an arbitrary version number and prevent inconsistencies in version numbers.

[0017]

According to one aspect of the present invention, there is provided a version management method for assigning a version number to a registered object and managing a group of objects including the object. Is registered, when a version number is specified for the registered object, the specified version number is assigned to the registered object.

According to a second aspect of the present invention, in the first aspect of the invention, when a version number is not specified for the registered object, a version number of an already registered object group is assigned. Features.

According to a third aspect of the present invention, in the first or second aspect, the object has a key attribute indicating a type of the object, and the version number is prepared for each of the key attributes. It is characterized by being given from a serial number.

Further, the invention of claim 4 provides the invention according to claims 1 to 3
In any one of the inventions described above, the latest version attribute is set for an object to which a maximum version number is assigned among the version numbers.

Further, the invention of claim 5 provides the invention according to claims 1 to 3
In any one of the inventions described above, when the specified version number is the same as the version number of an already registered object, an error is notified without registering the object.

Further, the invention of claim 6 is the invention of claims 1 to 3
In the invention according to any one of the first to third aspects, when the specified version number is the same as the version number of an already registered object, the object registered in the object with the version number is overwritten. And

Further, the invention of claim 7 is the invention of claims 1 to 3
In any one of the inventions described above, if the specified version number is the same as the version number of an already registered object, the specified version of the version numbers assigned to the registered object is After shifting all objects higher than the number to the higher order, a version number is assigned to the registered object.

[0024] Further, the invention of claim 8 is based on claims 1 to 3.
In any of the inventions described above, if the specified version number is the same as the version number of an already registered object, an error occurs without registering the object in advance or based on an instruction at the time of registering the object. , The process of overwriting the object registered in the object with the specified version number, and the process of overwriting the specified version number among the version numbers assigned to the registered object And a process of assigning a version number to an object registered after all of the objects are shifted to the higher ranks.

According to a ninth aspect of the present invention, in the third aspect of the present invention, when the key attribute is changed for an already registered object, the version number of the version number is assigned to the changed object. If specified
The specified version number is assigned to the object to be changed, and if no version number is specified for the object to be changed, the object is changed with reference to the version number of the already registered object group. It is characterized in that the object is given the maximum version number.

According to a tenth aspect of the present invention, in a version management apparatus for assigning a version number to a registered object and managing an object group including the object, when the object is registered, the registered object Receiving means for receiving the specification of the version number for the object, attribute reference means for referring to the version number of the already registered object group, specification of the version number received by the receiving means, and the version number referred to by the attribute reference means Version number determining means for determining a version number to be assigned to an object to be registered based on the above, and assigning the determined version number to the registered object. When the specification of the version number is accepted It is characterized by imparting to the objects that are registered with the specified version numbers.

According to an eleventh aspect of the present invention, in the tenth aspect of the present invention, the version number determining means, if the receiving means does not receive the specification of the version number, the version referred to by the attribute referring means. A number is given to the registered object.

According to a twelfth aspect of the present invention, in the tenth or eleventh aspect, the object has a key attribute indicating a type of the object, and the version number determining means prepares the key attribute for each of the key attributes. It is characterized in that a version number to be assigned to an object to be registered is determined from the registered serial number.

According to a thirteenth aspect of the present invention, in the invention according to any one of the tenth to twelfth aspects, based on the version number referred to by the attribute reference means, the object having the maximum version number is An attribute setting means for setting a version attribute is further provided.

According to a fourteenth aspect of the present invention, in any one of the tenth to twelfth aspects of the invention, the version number determining means includes the same version number as the version number of an object whose registered version number has already been registered. In this case, an error is notified without registering the object.

[0031] According to a fifteenth aspect of the present invention, in any one of the tenth to twelfth aspects, the version number deciding means is the same as the version number of the object in which the specified version number is already registered. In this case, the object registered in the object with the version number is overwritten.

According to a sixteenth aspect of the present invention, in any one of the tenth to twelfth aspects of the invention, the version number deciding means is the same as the version number of the object in which the specified version number is already registered. In this case, the version number is assigned to the registered object after shifting all of the version numbers assigned to the registered object that are equal to or higher than the designated version number to the higher order. I do.

According to a seventeenth aspect of the present invention, in any one of the tenth to twelfth aspects of the invention, the version number determining means is configured to determine that the specified version number is the same as the version number of an already registered object. In this case, a process of notifying an error without registering an object in advance or based on an instruction at the time of registering an object, and a process of overwriting an object registered in an object having a specified version number And shifting the version number assigned to the registered object higher than the specified version number, and then assigning a version number to the registered object. Processing is performed.

In a preferred embodiment of the present invention, when the key attribute is changed for an object that has already been registered, the accepting means sets the version number. If the specification of the version number is received, the specified version number is added to the object to be changed. If the receiving unit does not receive the specification of the version number, the version referred to by the attribute reference unit is used. The maximum version number is assigned to the object to be changed based on the number.

[0035]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a version management method and apparatus according to the present invention will be described below in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram showing a configuration of an object management apparatus to which the present invention is applied. As shown in FIG. 1, the object management apparatus includes a request processing unit 1, an object management unit 2, an object database 3, an attribute information database 4, and a version management unit 5.

The request processing unit 1 receives a processing request from an unillustrated client, such as registration of an object or change of an attribute, and requests the object management unit 2 and the version management unit 5 to perform processing according to the contents of the request.

The object management unit 2 receives the request from the request processing unit 1 and registers the object in the object database 3 and registers attribute information and the like of the registered object in the attribute information database 4. Also, upon request from the request processing unit 1 or the version management unit 5,
Reference and update of attribute information registered in the attribute information database 4 are performed.

The object database 3 and the attribute information database 4 store objects and their attribute information, respectively. Further, here, the object database 3 and the attribute information database 4 have different configurations.
The configuration may be the same. In the attribute information database 4, the attribute information may be managed in a table format, or may be managed without taking a table format as in an object-oriented database. The attribute information of the object does not necessarily need to be managed in a database, but may be managed using a text file or the like.

The version management unit 5 is a part to which the present invention is applied. Upon receiving a request from the request processing unit 1, the version management unit 5 determines a version number of an object to be registered, and performs consistency processing of the version number between objects. Do.

Here, the details of the version management section 5 will be described. FIG. 2 is a block diagram showing the configuration of the version management unit 5.

As shown in FIG.
Is a request receiving unit 5 that receives a request from the request processing unit 1
1, an attribute information reference unit 52 that references attribute information stored in the attribute information database 4 via the object management unit 2, a request received by the request reception unit 1, and attribute information referred to by the attribute information reference unit 52. A version determining unit 53 for determining the version number and the latest version of the object based on the attribute information stored in the attribute information database 4 based on the version number and the like determined by the version determining unit 53 via the object management unit 2. An attribute information updating unit 54 for updating is provided.

The version management unit 5 determines the version number of a newly registered object to the maximum as in the conventional one (see FIG. 3 (a)), and is different from the version number of the existing object. Assignment of consecutive version numbers (see FIG. 3B), assignment of lower version numbers than the latest version (see FIG. 3C), and updating of the latest version when the latest version of the object is deleted (see FIG. 3C) FIG. 3D) becomes possible.

Here, with reference to FIGS. 4 to 6, version management at the time of object registration will be described. 4 to 6 are flowcharts showing the operation flow of the version management unit 5 when registering an object.

In registering an object, first, the request receiving unit 51 receives a key attribute value and a specified version number of an object to be registered together with a request from the request processing unit 1 (step 101).

If the key attribute value is NULL (blank) (YES in step 102), the version determining unit 53 determines that no version number is assigned, and the object management unit 2 Is registered in the object database 3 without a version number (step 103).

If the key attribute value is not NULL (NO in step 102) and no version number is specified for the object to be registered (step 1)
04 (NO), an unspecified process is performed (step 105).

In the unspecified process, the attribute information reference unit 52 refers to the attribute information database via the object management unit 2 and obtains the maximum version number from existing objects having the same key attribute value (step 151).
As a result, when the object of the maximum version does not exist, that is, when there is no existing object having the same key attribute (NO in step 152), the version determination unit 53 determines the version number of the object to “1”. Then, the object management unit 2 receiving this registers the object with the version number “1” (step 153). Then, the attribute information updating unit 54 sets the latest version flag attribute indicating the latest version to the registered object via the object management unit 2 (step 154), and ends the object registration processing. The latest version flag attribute is set for the attribute information stored in the attribute information database 4.

If the maximum version of the existing object is found as a result of obtaining the maximum version in step 151 (YES in step 152), the version determining unit 53 sets the version number of the object to “maximum version + 1”. And the object management unit 2 having received the version number registers the object with the version number “maximum version + 1” (step 155). Then, after the attribute information updating unit 54 resets the latest version flag attribute set in the maximum version of the existing object via the object management unit 2 (step 156), the registered object indicates that it is the latest version. The latest version flag attribute is set (step 154), and the object registration processing ends.

On the other hand, if the key attribute value is not NULL (NO in step 102) and a version number is specified for the object to be registered (step 10).
(YES in step 106), the attribute information reference unit 52 refers to the attribute information database via the object management unit 2, and as a result, if there is an existing object having the same version number as the specified version number (YES in step 106). ),
The duplication process described later is performed (step 107).
3, the object management unit 2 determines the version number of the object to be the specified number, and registers the object with the specified version number (step 108).

At this time, if the specified version number does not become the maximum with respect to the version number of the existing object (NO in step 109), the registration process is terminated as it is, but the specified version number becomes the maximum. If so (YES in step 109), the attribute information updating unit 54 resets the latest version flag attribute set in the object of the existing maximum version via the object management unit 2, and updates the registered object with the latest version. Is set (step 110), and the object registration process ends.

In the duplication process, a process is performed on a duplicated version number by a preset method or a method designated for each request.

First, when the error processing is set or designated (YES in step 171), the error is notified to the request processing section 1 without registering the object (step 172), and the processing ends.

When the overwriting process is set or designated (NO in step 171 and YES in step 173), the version determining unit 53 registers the object with the version number designated in the object managing unit 2. Object to be overwritten (step 17
4), end the process. At this time, since the latest version does not change due to overwriting, the latest version flag attribute is not changed.

When the version change is set or designated (NO in step 171, step 17
(NO in 3), the attribute information updating unit 54 changes the version number of all the objects of the higher version than the specified version to “1” by adding “1” to all the objects by the instruction of the version determining unit 53 (step 17)
5) The version determining unit 53 determines the version number of the object to be the specified number, and the object management unit 2 receiving this determines the object with the specified version number (step 176). Also in this case, since the latest version does not change by the version change process, the latest version flag attribute is not changed.

Next, referring to FIG. 7, a description will be given of version management when changing the key attribute value of an object. FIG. 7 is a flowchart showing the flow of the operation of the version management unit 5 when changing the key attribute value of the object.

To change the key attribute value, first, the request receiving unit 51 receives a new key attribute value and a new version number to be changed from the request processing unit 1 (step 201). The old key attribute value of the target object is acquired from the attribute information database 4 via the unit 2 (Step 202).

Here, the acquired old key attribute value is NULL.
If it is not L (NO in step 203), if the target object is the latest version (for the old key attribute value) (YES in step 204), the attribute information updating unit 5
4 sets the latest version flag attribute to the next newest version of the object (with the old key attribute value) (step 205), and if the target object is not the latest version (NO in step 204), the old key attribute The value is deleted (step 206). Then, the attribute information updating unit 54 sets a new key attribute value for the target object (Step 207), and then performs version number adjustment processing (Step 208).

The process of adjusting the version number is the same as the process after step 101 described above.
The description here is omitted. However, steps 103, 1
In 08, 153, 155, and 176, “register object” should be read as “change attribute of object”. In addition, it is assumed that “registered object” in steps 110 and 115 is replaced with “object whose attribute is to be changed”.

On the other hand, if the old key attribute value obtained in step 202 is NULL (YES in step 203), a new key attribute value is set for the target object (step 207), and thereafter, the version number is adjusted. Processing is performed (step 208).

Although descriptions of processes such as object movement and copying are omitted, any process can be realized by combining the above-described process of registering an object and changing the key attribute value. Also, when deleting an object, if the target object is not the latest version, delete the object as it is. If the target object is the latest version, set the latest version flag attribute to the next new version of the object, Delete the target object.

By the way, the version determining unit 53 determines and determines various types of version numbers. As the version number, in addition to a number starting from 1 and a number starting from 0, symbols such as alphabets whose order is determined in advance can be used. The numerical version numbers are 1, 2, 3,. . . Not only integers such as 1.
1, 1.2, 1.2.1, 1.2.2. . . like,
It is possible to include minor versions that derive like branches and leaves from the main version.

In addition, by combining numbers and symbols, 1.1, 1.1
It is also possible to process version control systems such as a, 1.1b, 1.2.

Further, when the version number is changed when a minor version is included (step 17).
5), the version number is changed only for objects having the same version up to the end of the specified version number. For example, 1.2, 1.2.1,
In the state where the objects with the version numbers of 1.2.1.1, 1.2.
Registering an object with version number 2.1,
1.2.1 is changed to 1.2.2 and 1.2.1.1 is changed to 1.2.2.1, but 1.2.2, 1.2.
No changes to 2.1 will be made.

In the above embodiment, although not particularly mentioned, the key attribute value for determining the version number is:
A plurality of attribute values can be used as a set.

Further, version management can be performed in units of logical objects (cabinet, folder, binder, etc.). For example, version management can be performed only for a group of files included in a folder or the like. .

[0067]

As described above, according to the present invention, when an object registration request is received together with the specification of a version number, the version number of the existing object is referred to maintain the consistency of the version numbers. And the attribute of the object is set so that the latest version of the object is the only one.After registering the latest version of the object, the old version of the object can be registered. It is not necessary for the user to set the version number and information for identifying the latest version of the object.

Further, since the consistency of the version numbers is always maintained, it is not necessary to change the application even in a system in which an application using the consistency of the version exists.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an object management device to which the present invention has been applied.

FIG. 2 is a block diagram showing a configuration of a version management unit 5;

FIG. 3 is a diagram showing an example of version management.

FIG. 4 is a flowchart (1) showing a flow of an operation of a version management unit 5 at the time of object registration.

FIG. 5 is a flowchart (2) showing a flow of the operation of the version management unit 5 at the time of object registration.

FIG. 6 is a flowchart (3) showing the flow of the operation of the version management unit 5 at the time of object registration.

FIG. 7 is a flowchart illustrating a flow of an operation of a version management unit 5 when a key attribute value of an object is changed.

FIG. 8 is a diagram showing an example of conventional version management.

FIG. 9 is a flowchart showing a flow of version management at the time of conventional object registration.

FIG. 10 is a flowchart showing a flow of version management when changing a key attribute value of a conventional object.

[Explanation of symbols]

 1 request processing unit 2 object management unit 3 object database 4 attribute information database 5 version management unit 51 request reception unit 52 attribute information reference unit 53 version determination unit 54 attribute information update unit

Claims (18)

[Claims] 1. A version management method for assigning a version number to an object to be registered and managing an object group including the object, wherein when an object is registered, a version number of the object is registered. If specified
A version management method, wherein the specified version number is assigned to the registered object. 2. The version management method according to claim 1, wherein when no version number is specified for the registered object, a version number of an already registered object group is assigned. 3. The object according to claim 1, wherein the object has a key attribute indicating a type of the object, and the version number is assigned from a serial number prepared for each key attribute. The described version control method. 4. The apparatus according to claim 1, wherein a latest version attribute is set for an object to which a maximum version number is assigned among the version numbers.
Version control method described in any of the above. 5. The method according to claim 1, wherein when the specified version number is the same as the version number of an already registered object, an error is notified without registering the object. Version control method described in any of them. 6. When the specified version number is the same as the version number of an already registered object, the object registered in the object with the version number is overwritten. The version management method according to claim 1. 7. When the specified version number is the same as the version number of an already registered object, the specified version number is equal to or more than the specified version number among the version numbers assigned to the registered object. 4. The version management method according to claim 1, wherein a version number is assigned to a registered object after all objects are shifted to a higher order. 8. When the specified version number is the same as the version number of an already registered object, an error is notified without registering the object in advance or based on an instruction at the time of registering the object. Processing, overwriting the object registered in the object with the specified version number, and processing all the version numbers assigned to the registered object that are higher than the specified version number. 4. The version management method according to claim 1, wherein, after shifting to a higher rank, one of a process of assigning a version number to a registered object is executed. 9. When the key attribute is changed for an already registered object, if a version number is specified for the object to be changed, the specified version number is changed. When a version number is assigned to the object to be changed and no version number is specified for the object to be changed, the maximum version number is assigned to the object to be changed by referring to the version numbers of the already registered objects. 4. The version management method according to claim 3, wherein the method is provided. 10. A version management apparatus which assigns a version number to an object to be registered and manages a group of objects including the object, when the object is registered, accepts designation of a version number for the registered object. Receiving means; attribute reference means for referring to a version number of an already registered object group; objects registered based on the specification of the version number received by the receiving means and the version number referred to by the attribute reference means And a version number determining unit for determining the version number to be assigned to the registered object. The version number determining unit receives the specification of the version number by the receiving unit. If so, the designated Versioning apparatus characterized by imparting to the objects that are registered with the version number. 11. The method according to claim 11, wherein the version number determining unit, if the receiving unit does not receive the specification of the version number, assigns the version number referenced by the attribute referring unit to the registered object. The version management device according to claim 10. 12. The object has a key attribute indicating a type of the object, and the version number determining means determines a version number to be assigned to the registered object from a serial number prepared for each key attribute. 12. The version control device according to claim 10, wherein 13. An attribute setting means for setting an latest version attribute to an object to which a maximum version number is assigned based on a version number referred to by said attribute reference means. 1
The version management device according to any one of 0 to 12. 14. The method according to claim 1, wherein the version number determining unit notifies an error without registering the object when the specified version number is the same as the version number of the already registered object. The version management device according to claim 10, wherein 15. The version number determining means, if the specified version number is the same as the version number of an already registered object, deletes the object registered in the object to which the version number is assigned. 11. An overwriting method.
13. The version management device according to any one of claims 12 to 12. 16. The version number determining means, when the specified version number is the same as the version number of an already registered object, the version number of the version number assigned to the registered object. 2. The system according to claim 1, wherein a version number is assigned to an object to be registered after all the objects having the specified version number or more are shifted to a higher order.
3. The version control device according to any one of 2. 17. If the specified version number is the same as the version number of an already registered object, the version number determining means registers the object in advance or based on an instruction at the time of registration of the object. Notifying the error without performing the process, overwriting the object registered in the object with the specified version number, and specifying the version number specified in the version number assigned to the registered object. 13. A process for assigning a version number to an object to be registered after shifting all objects having a version number or higher to a higher rank, and executing any one of the following processes. Version control device. 18. The version number determining means, when the key attribute is changed for an already registered object, when the receiving means receives specification of a version number, If the version number is given to the object to be changed, and the receiving unit does not receive the specification of the version number,
13. The version management apparatus according to claim 12, wherein a maximum version number is assigned to the object to be changed based on the version number referred to by the attribute reference unit.