JPH06187206A - File control unit - Google Patents

Abstract

PURPOSE:To properly control the update of a file by using difference information between a base file and a version file. CONSTITUTION:This file control unit is equipped with a base file update indicating means 11 which indicates modification when access to a specific file meet base file update conditions, a base file update condition changing means 12 which changes the update conditions, an additional base file specifying means 13 which accepts addition, a base file registering means 14 which performs additional registration, and a base file specifying means 15 which specifies an efficient file for the version file. Further, the control unit is equipped with a reset base file specifying means 16 which accepts resetting, a base file registration resetting means 17 which resets the registration, a base file deleting means 18 which deletes a resetting-specified file, a version file restoring means 19 which restores the version file on the basis of difference information relating to the base file, a composite difference information specifying means 20 which accepts difference information to be composed, and a difference information composing means 21 which composes new difference information of the difference information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management device, and in particular, it is possible to update a series of files by using difference information between a certain predetermined base file and a file of a version adjacent thereto. The present invention relates to a file management device that can be appropriately managed.

[0002]

2. Description of the Related Art FIG. 11 is an explanatory diagram of an application example of a conventional technique of this type. In FIG. 11, a version N file (Nth version file as viewed from the original file) 111 recorded on an appropriate recording medium 110 is a file that is required to be changed by the user.
In response to the update operation 112A, a version N + 1 file (N + 1th version file as seen from the original file) 112 is generated. In the most basic of these types of techniques, a series of version files generated in this way is recorded / held on the recording medium 110 as it is, and the version of the file is Management is running.

FIG. 12 is an explanatory view of another application example of the conventional technique of this type. In FIG. 12, the oldest version file (or version 1 file) 121 stored in the recording medium 120 is used as a starting file, and the oldest version file 1
21 stores all data necessary for retrieval or processing. And the oldest version file 1
21 receives the required change / update operation 122A executed by the user based on the difference information for generating the version 2 file 122, and the version 2 file 122, which is the immediate target, is generated. Thereafter, similar operations are sequentially repeated, and the required change / update operation 123A executed by the user based on the difference information for generating the file 123 of the version N from the immediately previous version file is received, and the final goal is set. A certain version N file 123 is generated. In this another application example, it is not necessary to record all the information about some version files, and only the difference information necessary to restore the files of the adjacent versions is stored in the recording medium. This is advantageous because it improves the utilization efficiency of the recording medium.

By the way, in the above-mentioned conventional method, the oldest file is always recorded as the base file in the corresponding recording medium, and therefore, there is a problem in accessing the old version of the file. However, when performing access to a recent version file,
There is a drawback in that the restoration process with some difference information must be repeated toward the oldest version file as the base file. However, since the number of times that a newer version file is accessed is usually far greater than the number of times that an older version file is accessed, this difficulty is not so great for files with a particularly large number of versions. Get serious.

FIG. 13 is an explanatory view of still another application example of the conventional technique of this type. In FIG. 13,
The intermediate version file 131 stored in the recording medium 130 is specified by the user as a base file, and is suitable for generating a version file temporally older than the intermediate version file 131. The difference information is used to sequentially generate older version files. Then, in order to generate the oldest version file 132,
Required change / update operation 13 performed by the user based on the difference information indicating the difference from the version 2 file
In response to 2A, the final goal is to generate the oldest version file 132. Further, in order to generate a new version file temporally newer than the intermediate version file 131, the difference information suitable for that is used, and newer version files are sequentially generated. Then, in order to generate the latest version file 133, a required change / update operation 133A executed by the user based on the difference information indicating the difference from the immediately preceding version N-1 file is received, The latest goal is to generate the latest version file 133. What is particularly noted in this further application is that the designation of the base file is arbitrarily made by the user. And in such cases,
It is possible to specify a frequently accessed version file as the base file, which has the advantage of ensuring that the average access time to the targeted version file is reduced. In addition,
This further application example is disclosed in Japanese Patent Application Laid-Open No. 63-150745 [plural version management system] as a prior document.

FIG. 14 is an explanatory diagram of still another application example of the conventional technique of this type. In FIG. 14,
The latest version file 143 stored in the recording medium 140 is specified by the user as a base file, and this latest version file 143 (here, the file of version N) is always the base file regardless of the user's specification. Has been designated as. That is, in FIG. 14, the latest version file is always recorded as the base file, and there is the fact that the frequency of access to this version file is usually high, so the burden on the user is reduced accordingly. become. In FIG. 14, 141 is the oldest version of the file, and 141A is the difference information necessary to restore the oldest version of the file 141 from the version 2 file. Further, 142 is a version N-1 file, and 142A is difference information necessary to restore the version N-1 file from the version N file 143 which is the latest version file. Note that this further application example is disclosed in Japanese Utility Model Publication No. 4-20149 [electronic file system] as a prior document.

[0007]

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and (1) causes a user's trouble when a certain predetermined condition is satisfied. In addition, it is possible to automatically change to a more appropriate base file so as to minimize the overhead, and (2) according to the ambient conditions at the time of file access, the predetermined The condition of is automatically changed, and as a result, it is possible to determine a more appropriate base file; (3) Regarding the update time of the base file, for example, midnight, not when access to the target file occurs. It is possible to improve the operational efficiency of the system by selecting a time zone where the workload on the system is low; (4) Having multiple base files In addition, it is possible to efficiently generate a target version file by selecting a convenient one from the plurality of base files; (5) Generating a required version file based on a certain predetermined base file. The difference information used for this purpose is to be able to be efficiently organized and integrated depending on the access frequency of the predetermined base file and the like;

[0008]

The present invention has been made to achieve the above object, and a file management apparatus according to the present invention provides data necessary for generating a base file and difference information between versions. By holding it, each version of the file is generated.The base file can be changed from one version to another version. Base file automatic update instruction means (1) for instructing the change of the base file when the situation satisfies a predetermined base file update condition.
It is characterized by having 1). The file management device according to the present invention further comprises a base file update condition changing means (12) for changing the base file update condition when the above-mentioned situation satisfies a predetermined update condition change condition. It is characterized by that. The file management device according to the present invention includes an additional base file designation means (13) for accepting additional designation of a base file, and a base file registration means (14) for generating a file of the additionally designated version and additionally registering it as a base file. And a base file specifying means (15) for specifying a base file that is efficient for generating a required version of the file, and a plurality of base files are held, and the plurality of base files are held. It is characterized in that a convenient version is selected from the files to generate a target version file. A file management device according to the present invention includes a release base file designating means (16) for accepting a release designation of a base file, and a base file deregistration means (17) for deregistering a base file designated for release.
A base file deleting means (18) for deleting the base file designated for cancellation is further provided. The file management device according to the present invention, in place of the additional base file designation means (13), additionally designates a base file (with a condition) when the situation satisfies a predetermined base file addition condition. Means are further provided. The file management device according to the present invention, in place of the release base file designating means (16), designates the release of the base file when the situation satisfies a predetermined base file release condition (conditional) base file release designation. Means are further provided. A file management device according to the present invention is a combined difference information designating means (2) for accepting designation of difference information to be combined.
0) and difference information synthesizing means (21) for synthesizing the difference information designated for synthesis to generate new difference information. Further, the file management device according to the present invention, in place of the composite difference information designating means (20), specifies the composition of the difference information when the situation satisfies a predetermined difference information composition condition (with a condition).
It is characterized in that a difference information composition designating means is further provided.

[0009]

Since the file management device according to the present invention is configured to have the above-mentioned characteristics, it is possible to reduce the overhead without annoying the user when certain predetermined conditions are satisfied. To the minimum necessary,
A more appropriate base file can be automatically changed; the predetermined condition is automatically changed according to the surrounding conditions at the time of file access, so that a more appropriate base file can be determined. It is possible to improve the operational efficiency of the system by selecting the time when the base file is updated, not when the target file is accessed, but at a time when the workload on the system is low, such as at midnight. A plurality of base files are held, and by selecting a convenient one from the plurality of base files, it is possible to efficiently generate a target version file; based on a predetermined base file About the difference information used to generate the required version file by Allowing efficient consolidation by stomach tube or the like of the access frequency; advantages such results.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is an illustration of a schematic configuration centering on a file management apparatus according to an embodiment of the present invention. This Figure 1
In the above, what constitutes the file management device 1 is a request processing unit 1A which accepts an access request for a desired file from a client 2 such as an appropriate workstation and performs an appropriate processing; a predetermined processing for a version file to be processed. And a condition determining unit 1C that automatically performs a determination regarding a required condition for updating / deleting a base file when a desired version file is obtained.
A certain file 1D is connected to the version management unit 1B and the condition determination unit 1C.

FIG. 2 is a detailed block diagram of the version management unit in the above embodiment. In this FIG.
The base file update instructing section 11 is for instructing to automatically update to a more appropriate base file in accordance with the unevenness of access and the frequency of access in related version files. The base file update condition change instructing section 11 is for instructing to appropriately change the condition for updating the target base file according to the situation when executing the file access. The base file addition instructing unit 13 instructs to additionally specify a required base file when the number of related version files increases.
The base file registration unit 14 is for additionally registering a required base file when a file of a certain predetermined version is added. The base file specifying unit 15 specifies a base file that is particularly suitable for generating a required version file. The release base file designation section 16 designates a base file to be released when it is no longer needed, depending on the frequency of file access and the deviation of the version file to be accessed. The base file registration canceling unit 17 cancels the registration of the base file, which is no longer needed and is to be canceled, in order to delete it from a predetermined registration / storage unit. The base file deletion instructing unit 18 instructs to delete the unnecessary base file, for example, when the number of related version files decreases and the registration of the unnecessary base file is canceled. . The version file restoration unit 19 restores a required version file using necessary difference information based on a certain predetermined base file, for example. Composite difference information designation unit 2
0 is suitable for sorting out the difference information used to generate the version files that are successively adjacent to each other based on a certain predetermined base file when it becomes unnecessary according to changes in the file access implementation status. The difference information to be integrated is specified. The difference information synthesizing unit 21 is arranged in the synthetic difference information designating unit 20.
This is for synthesizing the difference information that is the object of integration.
Then, the difference information temporary storage unit 22 is a kind of memory means, and takes in the difference information necessary for restoring / creating the version file from the file 1D side and temporarily stores it.

FIG. 3 is a flow chart for explaining the mode of operation of the above embodiment. In this FIG.
When the file to be processed is updated after the embodiment is started by an appropriate method such as inputting a start command, the version management unit 1B asks whether the update condition of the base file is satisfied. Is output from the condition determining unit 1C (S31). In response to this, the condition determination unit 1C determines whether or not the change amount of the file based on the update of the requested file up to the present exceeds a predetermined reference limit (S3).
2). If the result of this determination is Yes, that is, if the amount of change in the file exceeds a predetermined reference limit, the process proceeds to the next step S33, and the file generated based on the update is As specified as a new base file, version management unit 1B
The base file update instruction unit 11 therein is caused to perform a required operation. On the other hand, when the result of the determination in step S32 is No, that is, when the file change amount does not exceed a certain predetermined reference limit,
The process proceeds to another step S34, and the changed amount of the file is used only as the difference information and stored in the difference information temporary storage unit 22 or the file 1D in the version management unit 1B.

FIG. 4 is a flow chart for explaining another mode of operation of the above embodiment. In FIG. 4, the version management unit 1B asks whether or not the update condition of the base file is satisfied when the file to be processed is updated after the embodiment is started in an appropriate manner. It is issued to the condition determination unit 1C (S41). In response to this, the condition determination unit 1C determines whether or not the number of file updates exceeds a predetermined reference limit (S42). When the result of this determination is Yes, that is, when the number of times the file has been updated exceeds a predetermined reference limit, the process proceeds to the next step S43, and the file generated based on the update is The base file update instruction unit 11 in the version management unit 1B is caused to perform a required operation so as to be designated as a new base file. On the other hand, when the result of the determination in step S42 is No, that is, when the number of times the file has been updated does not exceed a predetermined reference limit, the process proceeds to another step S44 and the file is updated. The change amount of the file is used only as the difference information, and the difference information temporary storage unit 22 or the file 1D in the version management unit 1B is used.
Will be stored in.

FIG. 5 is a flow chart for explaining another mode of operation of the above embodiment. In FIG. 5, the version management unit 1B asks whether or not the update condition of the base file is satisfied when the file to be processed is updated after the embodiment is started by an appropriate method. It is issued to the condition determination unit 1C (S51). In response to this, the condition determination unit 1C determines whether or not the elapsed time from the latest update time of a certain file exceeds a predetermined reference limit (S52). When the result of this determination is Yes, that is, when the elapsed time from the latest update time of the file exceeds a predetermined reference limit, the process proceeds to the next step S53 and based on the above update. The base file update instructing unit 11 in the version managing unit 1B is caused to perform a required operation so that the file generated by the above is designated as a new base file. On the contrary,
When the result of the determination in step S52 is No, that is, when the elapsed time from the latest update time of the file does not exceed a predetermined reference limit, the process proceeds to another step S54 and The changed amount of the file is used only as the difference information and stored in the difference information temporary storage unit 22 or the file 1D in the version management unit 1B.

FIG. 6 is a flow chart for explaining still another aspect of the operation of the above embodiment. In this FIG. 6, after the embodiment has been activated in a suitable manner,
Based on a predetermined request from the request processing unit 1A, the combined difference information designating unit 20 in the version management unit 1B operates as follows.
Some relevant difference information is designated as combined difference information so that only the difference information corresponding to a certain version is left, and a merge operation for these combined difference information is instructed (S61). In response to this, the difference information composition unit 15 in the version management unit 1B executes the merge operation for the composition difference information designated in the previous step S61 (S62). Step S6 following this
In No. 3, the difference information that is no longer necessary due to the execution of the merge operation is deleted from the difference information temporary storage unit 22 or the file 1D, and the new difference information created as a result of the execution of the merge operation is added to the above. It is stored in the difference information temporary storage unit 22 or the file 1D.

FIG. 7 is an exemplary diagram which contributes to grasping another mode of the operation of the above-mentioned embodiment in FIG. In FIG. 7, what is listed in the upper part (A) column is a certain predetermined base file 70, and some difference information 71, 72, 73, which are sequentially arranged with respect to this base file 70. 74, 75 and 76. Now, it is assumed that the difference information 72 and 73 is made unnecessary according to a certain predetermined reference limit, and the difference information 74 corresponding to a certain predetermined version is supposed to remain. At this time, the so-called unnecessary difference information 72, 73 is merged with the remaining difference information 74, and as shown in the lower part (B) column of FIG.
Only will survive. By doing so, unnecessary difference information is deleted from the file 1D as a recording medium, the recording medium can be used more efficiently, and an error in data processing occurs due to the presence of unnecessary information. Will also be reduced.

FIG. 8 is a flow chart for explaining still another mode of the operation of the above embodiment. In FIG. 8, after the above-described embodiment is activated in an appropriate manner, it is requested by a predetermined instruction from the request processing unit 1A to specify and record a certain predetermined version file as a base file (S81). . In response to this, in the version file restoration unit 19 in the version management unit 1B, various functional units related to the difference information (that is, the combined difference information designating unit 20, the difference information combining unit 21, the temporary storage unit 2).
The predetermined version file is restored on the basis of the existing base file and the difference information corresponding thereto while performing a required cooperative operation with other means such as 2) (S).
82). In subsequent step S83, the difference information corresponding to the specified predetermined version file is deleted from the difference information temporary storage unit 22 or the file 1D by the required operation in the various functional units relating to the difference information, The restored predetermined version file is recorded again as a base file in a predetermined portion of the file 1D as the recording medium.

FIG. 9 is an exemplary diagram which contributes to grasping another mode of the operation of the above-mentioned embodiment in FIG. In FIG. 9, what is listed in the upper (A) column is a predetermined existing base file 90A, a predetermined version file 90B, and some of the files sequentially arranged between them. Difference information 91, 92, 93,
94 and 95. Now, with the existing base file 90A as a reference, the difference information 91, 9 that follows
By using 2, 93 in combination, a new base file 90C is created and recorded in a predetermined portion of the file 1D as a recording medium, as shown in the lower row (B) of FIG. The difference information 93 corresponding to this is deleted as unnecessary and is deleted from the difference information temporary storage unit 22 or the file 1D.

FIG. 10 is an exemplary diagram which contributes to grasping another aspect of the operation of the above-mentioned embodiment in FIG. In FIG. 10, what is listed in the upper (A) column is a given existing base file 100C, a given version file 100A, 100B, and how many are sequentially arranged between them. The difference information 101, 102, 104 and 105.
Now, using the version file 100A in the previous stage of the existing base file 100C as a reference, and using the difference information 101 and 102 that follow, as shown in the lower column (B) of FIG. 10, The new difference information 103C is created and recorded in a predetermined part of the recording medium, and the existing base file 100C corresponding to this is deleted as unnecessary.

Although the embodiment of the present invention described so far includes the condition judging unit for judging the condition at the time of changing or updating the file, such as the number of times and history of file access, it is not limited to this. However, it is of course possible to omit the condition determination unit and leave the determination to the user as to whether or not a certain predetermined condition is important to the user.

[0021]

As described above, the file management device according to the present invention is a device for generating a file of each version by holding data necessary for generating a base file and difference information between versions. The base file is configured to be changeable from one version to another version. In addition, a plurality of base files are prepared, and the optimum one can be selected and used for creating the version file for the time being. Further, it is configured so that unnecessary difference information can be appropriately organized and integrated in view of the access frequency of the target version file. Thus, according to the file management device of the present invention, when a certain predetermined condition is satisfied, a more appropriate base is provided so as not to bother the user and minimize the overhead. Automatic change to the file is possible; the above-mentioned predetermined condition is automatically changed according to the surrounding situation when accessing the file, and as a result, a more appropriate base file can be determined. It is possible to improve the operational efficiency of the system by selecting the time when the workload of the system is low, such as midnight when the base file is updated, not when the target file is accessed. A plurality of base files are stored, and a convenient version is selected from the plurality of base files. The efficient generation of the difference information used for generating the required version file based on a certain predetermined base file is efficiently arranged according to the access frequency of the predetermined base file. Integration is enabled; and other effects are achieved.

[Brief description of drawings]

FIG. 1 is an exemplary diagram of a schematic configuration centering on a file management device according to an embodiment of the present invention.

FIG. 2 is a detailed configuration diagram of a version management unit in the above embodiment.

FIG. 3 is a flow chart for explaining a mode of operation of the above embodiment.

FIG. 4 is a flowchart for explaining another aspect of the operation of the above embodiment.

FIG. 5 is a flowchart for explaining another aspect of the operation of the above embodiment.

FIG. 6 is a flowchart for explaining still another aspect of the operation of the above embodiment.

FIG. 7 is an exemplary diagram useful for grasping still another aspect of the operation of the above embodiment in FIG. 6;

FIG. 8 is a flowchart for explaining still another aspect of the operation of the above embodiment.

9 is an exemplary diagram useful for grasping still another aspect of the operation of the above-described embodiment in FIG.

FIG. 10 is an exemplary diagram useful for grasping another mode of the operation of the above-described embodiment in FIG.

FIG. 11 is an explanatory diagram of an application example of a conventional technique of this type.

FIG. 12 is an explanatory diagram of another application example of the conventional technique of this type.

FIG. 13 is an explanatory diagram of still another application example of the conventional technique of this type.

FIG. 14 is an explanatory diagram of still another application example of the conventional technique of this type.

[Explanation of symbols]

1 --- File management device; 2--Client; 1A-
-Request processing unit; 1B-Version management unit; 1C-Condition determination unit; 1D-File; 11-Base file update instruction unit; 12-Base file update condition change instruction unit; 13-Base file addition Instruction unit; 14 --- Base file registration unit; 15 --- Base file specifying unit; 1
6 --- Cancellation base file designation unit; 17 --- Base file registration cancellation unit; 18 --- Base file deletion instruction unit;
19 --- version file restoring unit; 20 --- composite difference information designating unit; 21 --- difference information combining unit; 22 ---- difference information temporary storage unit.

Claims (8)

[Claims] 1. Data necessary for generating a base file,
A device that generates a file of each version by holding difference information between versions, and the base file is a device that can change from one version to another. A file management device comprising a base file automatic update instruction means for instructing to change the base file when the base file update condition is satisfied. 2. The file management device according to claim 1, further comprising base file update condition changing means for changing the base file update condition when the situation satisfies a predetermined update condition change condition. 3. An additional base file designation means for accepting additional designation of a base file, a base file registration means for generating a file of additionally designated version and additionally registering it as a base file, and generating a required version file. The file management apparatus according to claim 1 or 2, further comprising: a base file specifying unit that specifies a highly efficient base file, and holds a plurality of base files to generate a file from the efficient base file. 4. A release base file designation means for accepting a release designation of a base file, a base file registration canceling means for canceling the registration of the release-specified base file, and a base file deleting means for deleting the release-specified base file. The file management device according to claim 3, further comprising: 5. The file management apparatus according to claim 3, further comprising, instead of the additional base file designating means, a base file addition designating means for designating additional base files when a situation satisfies a predetermined base file addition condition. 6. The file management device according to claim 4, further comprising, in place of said release base file designating means, base file release designating means for designating release of a base file when a situation satisfies a predetermined base file release condition. 7. The composite difference information designating means for accepting designation of difference information to be synthesized, and the difference information synthesizing means for synthesizing the difference information designated for synthesis to generate new difference information. The file management device according to any one of claims 1 to 6. 8. A difference information combination designating unit for designating a combination of the difference information when the situation satisfies a predetermined difference information combination condition, instead of the combination difference information specification unit.
File management device.