JP3245047B2 - Version control apparatus and method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus and method for version management on a computer, and more particularly, to batch management of records of each generation (version) and management of update history.

[0002]

2. Description of the Related Art A file describing a parts list, an address book, and the like managed on a computer is updated stepwise through partial correction, addition, and deletion of records (data).

An example is shown in FIG. here,
The parts list (upper part) shown in FIG. 20 associates each part of a certain product A with a part name, and the parts list file (lower part) is a file in the storage device that represents the part list. In the parts list file, one part corresponds to one record (one data).

As shown in FIGS. 20A, 20B, and 20C, a product A is upgraded in the order of January 1, February 1, and March 1, and a parts list thereof is provided. Are sequentially corrected and updated, as a result, a plurality of component list files 2, 4, 6 having different generations (versions) are obtained.
Is created. Here, for example, it is also possible to create a next-generation parts list file by directly modifying the previous-generation parts list file, but in this case, since the file contents of the previous generation cannot be grasped after updating, In general, a part list file of the next generation is separately created by once copying a part list file of the previous generation and modifying it.

For example, Japanese Patent Application Laid-Open No. 2-93837 discloses a file management system similar to the above, in which files for each generation are separately created and stored. In such a method, generally, the current generation file is stored in a storage device (for example, a magnetic disk device) of the computer system in which the file is currently used, and the other files are stored in an external storage device or an auxiliary storage device (for example, Magnetic tape device, optical disk device, floppy disk device). This takes into account the capacity and frequency of use of the storage device.

In the conventional device, when a file of the previous generation is required, the file of the previous generation is loaded from an external storage device or the like to a storage device on the operating system, and thus temporarily and temporarily. The file to be used is switched by recalling the file to the system.

[0007]

However, according to the above-mentioned conventional method, even though there are many records having the same contents between the generations, those records are not stored between the generations. It was duplicated and managed. In particular, even files that were modified with only a few modifications after the previous generation file copy were often saved separately as separate generations. Therefore, there is a problem that the finite storage area cannot be used efficiently and the storage area is wasted. In addition, it is necessary to perform file management over a plurality of files, file recall processing from an external storage device, and the like, and it has been difficult to simplify file management. Furthermore, it is necessary to always save the entire new generation of files regardless of the amount of file modification, which makes file saving processing inefficient.

The present invention has been made in view of the above-mentioned conventional problems, and an object of the present invention is to eliminate the duplication of records common to each generation, thereby effectively utilizing the storage capacity of a storage device. It is an object of the present invention to provide a version management apparatus and method capable of streamlining generation management without switching files to be operated.

It is another object of the present invention to provide a version management apparatus and method capable of managing the generation of each record using attribute information that matches the temporal flow of generation.

Another object of the present invention is to correct a record.
It is an object of the present invention to provide a version management apparatus and a method which can easily perform deletion and the like, and can surely retrieve records of each generation even by such a change in record contents.

[0011]

In order to achieve the above object, according to the present invention, there is provided a version control apparatus for managing a record group of each generation updated step by step. An attribute assigning unit for assigning attribute information as date and time information indicating only a generation to which the record first belongs, and a generation integration in which each record to which the attribute information is assigned is stored in association with a search key item A file and, when a new generation record group is created, additional means for additionally storing only the corrected records corrected in the record group in the integrated file ;
New attribute information that has the same content as the record
And a deletion mask record with a deletion flag
A deletion unit for additionally storing the integrated generation file; and a search for a specific generation record from the integrated generation file based on the attribute information.
The record to which the latest attribute information was added after returning from the search date and time
Means for retrieving the delete mask record.
Is found, no record exists in the search key field.
Record search means for performing a search process as a non-existent record, wherein a common record is shared between generations in the generation integrated file.

According to the above configuration, in order to manage the generation of each record, attribute information is set for each record, and a search for a specific generation is performed on the generation integrated file based on the attribute information. The attribute information is information indicating the generation to which the user first belongs, and it is desirable that the attribute information be information meaning temporally before and after. Here, records belonging to each generation are stored and stored in the generation integrated file.
Although registered, a record common to each generation is shared by the plurality of generations. In other words, the generation integrated file contains
Only records that have not been stored until then are additionally stored, and duplicate registration of the same record is eliminated. Therefore,
According to the present invention, the storage capacity of the storage device can be efficiently used, and according to the present invention, records of each generation can be collectively managed using basically only a single file. It becomes unnecessary to read the file. That is, generation management can be simplified and speeded up.

In a preferred aspect of the present invention, the attribute information is preferably date and time information. According to the date and time information, each generation can be managed in terms of time, and retrieval can be performed by specifying the date and time. In other words, this is convenient when it is desired to know the product specifications at a certain time when the generation itself is unknown.

In a preferred aspect of the present invention, each record in the generation integrated file is managed for each search key item, and one or a plurality of records are associated with each search key item. That is, only the initial record is associated with the search key item having no record change, and the number of changed records according to the number of changes is associated with the search key item having the record change in addition to the initial record. Each record is managed by attribute information such as date and time information, and a record valid for each generation is specified before and after the attribute information.

In a preferred aspect of the present invention, the record search means searches for a record to which the latest date and time information is added after returning from the search date and time for each search key item. That is, for each search key item, if the record closest to the search date and time is searched, the record belonging to the closest generation before the search date and time can be specified. As described above, according to the present invention, there is an advantage that a record of a desired generation can be searched only by giving approximate information without designating the generation number itself. Therefore, even those with little knowledge of the file contents can easily perform the search operation. In a preferred aspect of the present invention, there is provided a deletion unit for deleting unnecessary records. here,
The deletion means desirably additionally stores a deletion mask record having the same contents as an unnecessary record and having new attribute information and a deletion flag added to the unified generation file.

According to the above configuration, when the deletion mask record is stored in the unified generation file, the generations after that are determined based on the attribute information (date and time information) set for the deletion mask record. Are excluded from the search. Therefore, there is an advantage that a similar result can be obtained without actually deleting records, and deletion can be managed for each generation.

That is, in a preferred aspect of the present invention, when the deletion mask record is searched, the search means performs a search process assuming that no record exists in the search key item.

In a preferred aspect of the present invention, further, a work file generating means for generating a work file by copying the contents of the generation integrated file, and creating a new generation record group based on the contents of the work file. Record correction means.

According to the above configuration, the file can be updated based on the file on which the records of all the generations are reflected. After the update, only the modified record changed by the adding means is automatically updated. Extracted,
It is additionally registered in the original generation integrated file.

In a preferred aspect of the present invention, there is provided interactive modification means for sequentially creating modification records with reference to the generation integrated file, and the adding means stores the correction records in the generation integrated file. Additional storage.

That is, the record is corrected for each search key item, so that the time required for file copy or the like can be deleted, and efficient data processing of only the corrected portion can be performed.

In a preferred aspect of the present invention, the date and time information is information indicating a date and time when each record is valid.
The date and time information may be an update date and time, but by specifying some past or future date and time, various generation managements can be performed in conjunction with the date and time search. For example, if the date and time information is adjusted at the time of product shipment, it is possible to match the specification and generation of the actually distributed product.

Further, in the method according to the present invention , in a version management method for managing a record group of each generation updated stepwise, each record may be stored before storing each record.
Date and time information indicating only the generation to which it belongs first for each code
Providing attribute information as information,
While assigning each assigned record to a search key item,
Process of storing in a new integrated file and a new generation of records
Was created and modified in that set of records
A process for additionally storing only correction records in the integrated file
The new record has the same content as the record that is no longer needed.
Deletion mask with new attribute information and deletion flag
Additionally storing a code in the generation integrated file;
From the generation integrated file, based on the attribute information,
Each search key item to search for records of a specific generation
Each time, the newest attribute information is returned from the search date and time.
Searching for a deleted record, wherein the deletion mask
When a record is found, the record is
And performing a search process assuming that the code does not exist.
The generation integrated file contains a record that is common to all generations.
Is shared . According to this configuration,
As described above, duplicate data registration can be avoided, and generation management can be simplified.

[0024]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a conceptual diagram showing the overall configuration of a version control device according to the present invention. First, the configuration of the apparatus will be described with reference to FIG.
The operation of each configuration will be described with reference to FIGS.

(A) Description of Apparatus Configuration In FIG. 1, the generation integrated file 1 shown in the center is shown.
0, as shown in FIG. 2 and FIG. 3 described below, associates date and time information with a data entity for each search key item. The file creation unit 12 creates a new file 14 of an initial generation (first generation) to be first registered in the generation integrated file 10. The file creator 12 includes an input device, database creation software, and the like. The created new file 14 is shown in FIG.
Is registered in the generation integrated file 10 as shown by the numeral 100. Prior to this, date and time information is added to each search key item. The date and time information functions as attribute information for managing the generation to which each record belongs. As the date and time information, specifically, the date and time when the file is created, the date and time when the file is valid, etc. It is appropriately selected.

The generation integrated file 10 constitutes a single file for each generation, and records common to each generation are shared between the generations. This will be described in detail later.

When the file is updated, that is, when the next generation is created, first, the generation integrated file 10 is copied as indicated by 102 in FIG. 1 by means (not shown) for creating the work file 24. Then, the work file 24 is formed as a so-called transaction file. The contents of the record that needs to be modified by the modification unit 26 are changed in the work file 24. Specifically, the search key item to be changed is specified, and the content of the data entity associated with the search key item is changed. The correction unit 26 includes, for example, an input unit and software that changes the contents of the database.

The work file 2 which has been modified as described above
4 is sent to the changed record extracting unit 28, and the changed record extracting unit 28 specifies the record whose contents have been corrected, and extracts only that record. That is, in the present embodiment,
In order to register only the difference between the generations, that is, the changed records, in the generation integrated file 10, the process of extracting the corrected changed records is performed. The correction unit 26
It is desirable to perform a process of automatically making the date and time information of the corrected record blank or the like in the correction work on the work file 24 by the user. According to such blanking of the date and time information, the changed record can be easily specified in the changed record extracting unit 28, and the complicated operation of comparing the contents of the modified work file 24 and the generation integrated file 10 is complicated. Is avoided.

Records existing only in the next generation extracted by the change record extraction unit 28 are additionally registered in the generation integrated file 10 as shown by 104 in FIG.
Prior to this, date and time information is added to the changed record by the date and time setting unit 30. The date and time setting unit 30 has the same function as the above-mentioned date and time setting unit 16, but the date and time information to be set is different from the date and time information initially set, and basically the date and time information is set first. Date and time information after the date and time information is set. With such a setting, it is possible to know the generation in which each record becomes valid first for each record. The date and time setting unit 16 and the date and time setting unit 30 are configured by, for example, a program for adding the date and time input by the user to each record.

By repeatedly performing the above-described file correction work as necessary, the first generation record and the subsequent generation records are integrated and stored in the generation integrated file 10, and the generation generation file 10 stores the first generation record and the subsequent generation records. Each record can be managed collectively.

In the present embodiment, as shown by the first modification adding unit 20 in FIG. 1, a method of modifying the generation integrated file 10 once by copying it as the work file 24, and a method of modifying the second modification in FIG. As shown by the section 22, there are two methods, a method of performing a necessary search from the generation integrated file 10 and a method of sequentially reading the data entity of the key item and correcting it. The second modification adding unit 22 will be further described. The data entity of the designated search key item is read by the interactive modification unit 32 as shown by 106 in FIG. The new record is registered in the generation integrated file 10 as indicated by 108 in FIG. The addition determining unit 34 determines whether the record to be added is appropriate, that is, whether the identification code of the record determined by the search, the key item, and the date and time information is unique. It is determined whether or not it exists, and if it is unique, the addition is permitted. The modification and addition of a record will be described later in detail.

The deletion unit 36 deletes unnecessary records from a certain generation in the integrated generation file 10. In the embodiment shown in FIG. 1, a deletion flag is set for unnecessary records in the work file 24. Is given. Records flagged for deletion
The change record extraction unit 28 extracts the
As shown by reference numeral 4, it is additionally registered in the generation integrated file 10. Of course, in this case, new date and time information is set by the date and time setting unit 30 for the record to which the deletion flag has been added. This will be described later in detail.

In the embodiment shown in FIG. 1, the work file 24 is shown as a processing target of the deletion unit 36.
Of course, the deletion process may be performed by sequentially specifying records in the generation integrated file 10 and adding a new record with a deletion flag set.

The search unit 40 targets the generation integrated file 10 in which records are integrated and managed over a plurality of generations.
With reference to the search date and time specified by the user by the search date and time specification unit 42, records of the generation indicated by the search date and time are searched for in search key item units. That is, in the generation integrated file 10, each record is managed for each search key item, and the record having the closest date and time information is searched for in each search key item with the search date and time being maximum. The search result of the search unit 40 is output as the file 44 of the specified generation.

The interactive correction unit 32 is composed of a display, an input device, a program for executing an interactive correction process, and the like, and the addition determining unit 34 and the search unit 40 are basically composed of a program for executing the same. Is done. Further, the search date / time specifying unit 42 is configured by an input device such as a keyboard.

As described above, the embodiment shown in FIG. 1 is applicable to a normal computer, and is applicable to database management in which file contents are updated step by step.

(B) Description of Operation Next, the specific operation of each configuration shown in FIG. 1 will be described with reference to FIGS.

The examples shown in FIGS. 2 to 18 are for the case where the version management method according to the present invention is applied to the management of vehicle specifications. As we all know, the specifications of automobiles vary a lot due to the demand for diversification of users,
In such a case, the version management according to the present invention is particularly effective.

(B1) Creation of New File First, a new file 14 constituting the first generation is created by the file creation unit 12 shown in FIG. The created new file is shown in FIG. This file is a file for specification management as described above, and for each search key item corresponding to the specification of the vehicle, a data entity indicating the use start date and time as the date and time information (attribute information) and the actual use content corresponds. Attached. For example, as the search key items, installed engine, total displacement, body shape, capacity, ...
Are defined, and the data entity is S
OHC 4-cylinder, 1809CC, monocoque 4-door, 5
.., Etc. are associated with each other. here,
The search key item can be arbitrarily specified by the user, and a data entity is input by the user for each of the specified search key items.

As shown in FIG. 2, after the registration of all data entities is completed and the new file 14 shown in FIG. 1 is completed, the date and time setting unit 16 sets the use start date and time for each search key item. Setting is given. Here, the date and time when the first determined specification becomes valid is input as the use start date and time, that is, the same 1996100100000 is set for each search key item as shown in FIG. This means 00:00 AM on October 1, 1996. In this embodiment, the date and time means the date and time when the product is shipped to the market. Of course, an arbitrary date and time can be set according to the use form of the file. However, it is necessary to add the same date and time information to each search key item constituting the first generation, and if a record of each generation is added after that, an additional record for each generation is added at the time of addition. Must be given the same date and time information.

Incidentally, the date and time information can be artificially given as described above, but can be automated by using, for example, the entry date and time.
As shown in FIG. 3, after the first generation file is completed,
As shown by 100 in FIG. 1, the file is registered in the generation integrated file 10.

(B2) First Example of Record Modification Next, creation of a second generation based on the first generation, that is, modification of a record will be described. FIG. 4 shows an example of the three specifications (search key items) of the engine, the total displacement, and the brake, showing an old specification and a new specification. Such changes are stored in the generation integrated file 1
In order to reflect this to 0, first, as shown in FIG. 1, the generation integrated file 10 is copied, and the work file 24 is created. The contents of the copied work file 24 are shown in FIG. 5, and the hatched portion shown in FIG. 5 indicates a change target. For such a work file 24, the data entity of the three search key items described above is changed by the correction unit 26. FIG. 6A shows the same file contents before change as shown in FIG. 5, and FIG. 6B shows the file contents after change. The correction unit 26 performs a process of automatically blanking the date and time information (use start date and time) of the changed record. Of course, by inputting a specific numerical value such as 0 or 9 in all digits, it may be identified that the record is a record to be changed.

In this correction work, the user changes the data entity of a specific search key item using a keyboard or the like while viewing the contents of the work file 24 displayed on the display, for example, so that the changed contents are changed. The contents are automatically recognized by the correction unit 26 and the contents of the work file 24 are updated.

The work file 24 having the contents changed as described above is stored in the change record extraction unit 28 as described above.
, Where only the records to be changed are extracted as shown by the hatching in FIG. 6B. In parallel with this, the use start date and time different from the use start date and time given by the date and time setting unit 30 in the first generation, for example, the date and time when a product having the changed specification is actually shipped to the market is changed. Is given to the record that was created. Then, only the change record to which such use start date and time is added is newly registered in the generation integrated file 10. FIG. 7 shows the state of the additional registration. As shown in FIG. 7, a record belonging to only the second generation indicated by shading is added. Specifically, two data entities are associated with the search key item of the mounted engine. Two data entities are also associated with the total displacement and the brake, respectively. Of course, the use start date and time assigned to those data entities are different between the first generation and the second generation. Incidentally, for the items other than the search key items changed in this way, the records are shared by the first generation and the second generation.

(B3) Second Example of Record Correction The above-described correction work was performed by the first correction adding section 20 shown in FIG. 1, but next, as another embodiment, by the second correction adding section 22. The correction operation will be described.

When the interactive correction unit 32 shown in FIG. 1 is activated, a search screen is first displayed on the display as shown in FIG. In the search screen, an input field for a specified search key item is displayed. Therefore, the user uses a keyboard or the like to enter the contents of a specific search key item. Then, the interactive correction unit 32, as shown in FIG.
The first generation file registered in the generation integrated file 10 is accessed, and the data entity corresponding to the input search key item is read. In the examples shown in FIGS. 8 and 9, since the mounted engine is specified as the search key item, the SOHC4 cylinder is read as the data entity. In this case, the use start date and time are blank as shown in FIG. 9, and the data entity and the use start date and time are input and designated by the user as shown in FIG. As a result, the data entity of the search key item has been changed and a new use start date and time has been given, so the interactive correction unit 32 additionally registers the record in the generation integrated file 10 via the addition determination unit 34 ( See FIG. 11). However,
Prior to the additional registration, the addition determination unit 34 determines whether the record content is appropriate. Specifically, one combination of the search key item and the use start date and time is specified on the generation integrated file 10. Additional registration is allowed only in such cases.

Then, as described above, if the correction operation for each search key item is repeatedly performed by the interactive correction unit 32, as shown in FIG. 12, the generation integrated file 10 in which only the first generation is registered is deleted. Thus, the second generation can be additionally registered. In the example shown in FIG. 12, similar to the example shown in FIG. 7, new records are registered for the mounted engine, the total displacement, and the brake. In FIG. 12, a shaded portion indicates an additional record.

In the sequential correction by the interactive correction unit 32 for each search key item, the same use start date and time are set for each record corrected at the same time. The setting may be performed artificially as described above, but it is also possible to automate the setting.

(B4) Deletion of Record Next, the deletion of a record that is unnecessary in the next generation will be described. In the present embodiment, when a record that existed in the previous generation becomes unnecessary in the next generation, the deletion target is specified by setting a deletion flag on the record to be deleted as described above. In this case, if a record to be deleted is simply deleted from the generation integrated file 10,
Since information about the generation before the deletion is lost, in the present embodiment, as shown in FIG. 14, for the same search key item, a data entity having a different use start date / time (date / time information) and the same content A new record (deletion mask record), in which a deletion flag is associated with a new record, is newly registered to perform the deletion process. Hereinafter, a specific description will be given.

FIG. 13 shows the contents of the generation integrated file 10 in which the second generation is registered. Here, the record indicated by 204 is a record to be deleted in the third generation. In the present embodiment, when the record 204 is to be deleted by the third generation, the work file 24 is first created by copying the generation integrated file 10, and the work file 24 is newly deleted by the deletion unit 36. An additional deletion mask record is created. This state is shown in FIG. Record 206 is a deletion mask record, and record 2
In order to mask 04 in the third generation, the same data entity, a different use start date and time, and a deletion flag are added to the same search key item. That is, record 204 and deletion mask record 2
06, only the use start date and time is different. As described later in detail, when a search date and time corresponding to the third generation is set, the record 206 is specified as the data entity of option 2 However, since the record 206 is provided with a deletion flag, the option 2 is processed as if no record exists. That is, record 20 is
By superimposing No. 6, the record whose use start date and time is earlier is hidden in data search. Of course, if the search date and time is set before the use start date and time corresponding to the third generation, the record 204 becomes the search target.

As described above, a specific record is deleted from a specific generation in data retrieval without changing or deleting the original record by additionally registering a deletion mask record to which a deletion flag is added. It becomes possible.

(B5) Search Processing Next, search processing by the search unit 40 shown in FIG. 1 will be described.

FIG. 15A shows the contents of the generation integrated file 10 in which the above-described record correction or deletion has been performed, that is, a plurality of generations have been registered. This figure 1
In the file contents shown in FIG. 5A, some of the search key items correspond to a plurality of data entities, and the option 2 is provided with a deletion flag.

FIG. 15B shows, for reference, the generation in which each record is shared. In addition,
The number indicated as the shared generation indicates the generation number.

In the present embodiment, when searching for records of each generation, the user does not need to be particularly aware of the generation number. An equivalent date and time can be specified as the search date and time. Then, on the basis of such designation, a record with the closest use start date and time as the maximum is specified for each search key item.

For example, when the first generation search is performed on the integrated generation file 10 having the file contents shown in FIG. 15A, the search date and time, for example, December 31, 1996 is specified. Specifically, 199 is set as the search date and time.
Enter 6123100000. Then, as shown in FIG. 16, the record closest to the search date and time is specified for each search key item with the search date and time set to the maximum. In FIG. 16, the searched records are shaded. As shown in FIG. 16, for example, for the search key item “installed engine”, records corresponding to the second generation are ignored, and only records corresponding to the first generation are extracted.

When the second generation is searched, for example, December 31, 1999 is designated as the date and time corresponding to "at that time" when information at that time is desired. Specifically, the search date and time is set to 1
Enter 99912310000000. Then, the search unit 40 specifies the record closest to the specified search date and time to the specified search date and time for each search key item. The state is shown by hatching in FIG. As shown in FIG. 17, for example, for the “installed engine” of the search key item, a second generation record is extracted.

When the third generation is searched, December 31, 2001 is designated as the "that time". More specifically, the search date / time designation unit 42 is used to input 20001123100000 as the search date / time. Then, the search unit 40 searches the generation integrated file 10 and extracts only records belonging to the third generation as shown in FIG. The searched records are shaded in FIG. In this case, as shown in FIG. 18, for the option 2 of the search key item, the search unit 4
A value of 0 specifies a record to which a deletion flag has been added. However, since the deletion flag has been added to the record, the search unit 40 performs a search process for option 2 assuming that the record does not exist.

As described above, by the vague specification of the search date and time, the record of the same date and time as the search date and time or the closest date and time can be extracted, whereby the record of the desired generation can be extracted, and the operability of the user can be improved. There is an advantage that can be improved.

FIG. 19 is a flowchart showing the operation of the search unit 40 shown in FIG. In S101, the search date and time designated by the user by the search date and time designation unit 42 is read. In S102, 1 is assigned as an initial value to n indicating the order of the search key items.
In S103, all records are extracted from the nth search key item, and in S104, the latest record before the search date and time among the extracted records is determined. In S105, it is determined whether or not a deletion flag is added to the record determined in S104. If the deletion flag is added, S107 is executed as it is. On the other hand, if the deletion flag is not added. S
In 106, the record determined in S104 is temporarily stored as the record of the search key item.

In S107, it is determined whether or not the record search has been completed for all items. If not, the value of n is incremented by one in S108, and the steps from S103 are repeatedly executed. . Then, when it is finally determined in S107 that the search has been completed for all items, a file composed of the record group of the specified generation is output.

[0063]

As described above, according to the present invention,
Duplicate registration of records common to each generation can be eliminated, thereby effectively utilizing the storage capacity of the storage device, and management of each generation can be integrated and performed without switching files between generations. There is an advantage.
Further, according to the present invention, there is an advantage that generation management of each record can be performed using attribute information such as date and time information that matches the generation. Further, according to the present invention, there is an advantage that records can be easily modified or deleted, and records of each generation can be reliably stored and retrieved even by such changes in the contents of records.

Further, according to the present invention, it is possible to extract a record of a desired generation by specifying an approximate date and time without specifying the generation itself, and there is an advantage that the burden on the user at the time of retrieval can be reduced. .

[Brief description of the drawings]

FIG. 1 is a conceptual diagram showing an overall configuration of a version management device according to the present invention.

FIG. 2 is a diagram showing a state in which registration of a data entity has been completed in creating a first generation file.

FIG. 3 is a diagram showing a state where a first generation file is completed.

FIG. 4 is a diagram showing search key items and their correction contents.

FIG. 5 is a diagram showing the contents of a file including a record to be modified.

FIG. 6 is a diagram showing the contents of a file before data is updated and the contents of the file after the data is updated.

FIG. 7 is a diagram showing the contents of a file to which a second generation has been added.

FIG. 8 is a diagram showing a search screen displayed when a record is modified in an interactive format.

FIG. 9 is a diagram showing designation of a search key item on a search screen and reading of a data entity of the designated search key item.

FIG. 10 is a diagram showing input of a use start date and time and a data entity by a user.

FIG. 11 is a diagram showing the contents of a file to which a record has been added.

FIG. 12 is a diagram showing the contents of a file to which a second generation has been added.

FIG. 13 is a diagram showing the contents of a file in which up to the second generation is registered.

FIG. 14 is a diagram showing the contents of a file in which a deletion mask record is registered in the third generation.

FIG. 15 is a diagram illustrating the contents of a file in which records are shared by multiple generations and the generation in which each record is shared.

FIG. 16 is a diagram showing a first generation search result.

FIG. 17 is a diagram showing search results of the second generation.

FIG. 18 is a diagram showing a third generation search result.

FIG. 19 is a flowchart illustrating an operation of a search unit.

FIG. 20 is a diagram showing a conventional version management method.

[Explanation of symbols]

10 generation integrated file, 12 file creation unit, 14
New file, 16 date and time setting part, 24 work file, 26 correction part, 28 change record extraction part, 30
Date and time setting part, 32 interactive correction part, 34 addition judgment part,
40 search part, 42 search date and time designation part.

Continuation of the front page (58) Field surveyed (Int. Cl. ⁷ , DB name) G06F 12/00 517 G06F 12/00 520 G06F 17/30 370 G06F 17/24 554

Claims (5)

(57) [Claims] 1. A version management apparatus for managing a record group of each generation updated stepwise, wherein prior to storage of each record, date and time information indicating only the generation to which the record first belongs for each record. an attribute assigning means for assigning the attribute information, each record said attribute information has been granted to the search key item
A generation integrated file that is stored while being correlated, and an additional unit that, when a new generation record group is created, additionally stores only the corrected records corrected in the record group in the integrated file, is unnecessary. New attribute with the same content as the record
Delete mask record with gender information and delete flag
From the generation integrated file based on the attribute information,
Each search key item to search for records of a specific generation
Each time, the newest attribute information is returned from the search date and time.
Means for searching for a deleted record, wherein the deletion mask
When a record is found, the record is
A record search means for performing a search process assuming that no code exists , wherein a common record is shared between generations in the generation integrated file. 2. A work file generating means for generating a work file by copying the contents of the generation integrated file, and a record correcting means for creating a new generation record group based on the contents of the work file. The version control device according to claim 1, wherein: 3. An interactive modification unit for sequentially creating modification records while referring to the generation integration file, wherein the addition unit additionally stores the modification records in the generation integration file. The version management device according to claim 1. 4. The version management apparatus according to claim 2, wherein the date and time information is information indicating a date and time when each record is valid. 5. A version management method for managing a group of records of each generation updated in a stepwise manner, wherein each record is stored for each record prior to storage of said record.
Attribute as date and time information indicating only the generation to which the user first belongs
Assigning information, and each record to which the attribute information is assigned is used as a search key item.
The process of storing in the generation integrated file while associating, and when a new generation record group is created, the record
Only the modified records that have been modified in the group
To add a new attribute to the
Delete mask record with gender information and delete flag
Additionally storing in the generation integrated file,
Based on the attribute information, the specific world
In order to search for records of each generation, for each search key item,
Return from the search date and time
Searching for a code, wherein the deletion mask record is
When the search key is found, the search key item contains no record.
Comprising a step of performing a search process as missing, and the generation integrated common record co between generations in the file
Version control method characterized by having.