JP4728073B2 - Database change point searching method and apparatus - Google Patents

Description

  The present invention relates to a database change point search method and apparatus for searching for a change point in a file before change and a file after change stored in a database.

  Conventionally, in building monitoring systems, for example, monitoring point names and numbers, data types, etc. are set in order to collect data from the monitoring points of various types of equipment such as air conditioning equipment, power equipment, crime prevention equipment, and disaster prevention equipment. Electronic data (general-purpose electronic data, hereinafter referred to as form data) is created in advance. The central monitoring device of the building monitoring system identifies the monitoring point from which data is to be collected based on the form data, and collects data from the monitoring point.

  By the way, in the building design stage and the construction stage, the change of the equipment type is frequently performed due to the design change, and accordingly, the contents of the monitoring points are changed and the number of monitoring points is frequently increased or decreased. When such design changes overlap, it becomes necessary to check whether the data capacity of the number of registered monitoring points is within the specification range of the central monitoring device. You may want to check for changes in numbers. At the time of this confirmation, in the changed form data, the changed part is often not displayed so that the changed part is clearly understood. Conventionally, the person compared the form data before the change with the form data after the change. Manual confirmation work such as finding differences (changes) in registered contents.

Since the work to check the change history of such monitoring points does not know the changed part, it is a manual check such as comparing all data, so it takes considerable effort to find the changed part. It was. Furthermore, when the number of monitoring points is large, and when the change points and the change frequency are large, considerable labor is generated, and as a result, there is a problem that work time is very long.
In addition, at the time of design change, the change contents may not be correctly input into the form data due to human error. It is also a problem that human error such as the input error remains undetected, especially when the monitoring point changes overlap and the number of monitoring points is large.
In particular, a large-scale building or the like generally has a large number of monitoring points, and thus the above problems tend to occur frequently.

  As a method for saving labor for confirming such changes, a method of extracting difference data between data before and after the change has been proposed (see, for example, Patent Document 1).

Japanese Patent Laid-Open No. 9-81427

  As described above, when checking the changes manually, there is a problem that it takes a lot of labor and time to find the changes, and there is a possibility of overlooking input errors in the form data. there were.

  On the other hand, according to the method disclosed in Patent Document 1, it is possible to save labor for confirming a change point. However, in the method disclosed in Patent Document 1, for example, data that has a large number of data (number of monitoring points) and a large number of data items (fields) such as form data used in a building monitoring system is changed. There was a problem that it was not suitable for the work to confirm. The reason why the method disclosed in Patent Document 1 is not suitable for the work of confirming form data has been changed because the method disclosed in Patent Document 1 displays difference data only for specified data items. This is because it is difficult to confirm which monitoring point the data is. The above problems are not limited to form data, but similarly occur in a file having a large number of data and data items.

  The present invention has been made in order to solve the above-described problem, saves the confirmation work of the change point, and can easily recognize the change point even for data having a large number of data and data items. It is an object of the present invention to provide a method and apparatus for searching for changes.

The database change point search method of the present invention includes a plurality of fields to be searched for change points designated from the outside and a preset key for each of the first file before change and the second file after change. A first step of reading a field; a second step of storing data of the read field of the first file; and storing data of the read field of the second file; A third step of selecting data having the same field information from the data of the first file and the data of the second file stored in the second step, and the two selected in the third step. A fourth step of comparing data for each common field other than the key field, and the comparison of this fourth step As a result, when the information does not match in any field, as a result of comparison between the fifth step storing this field as a change point and the fourth step, the information does not match in any field. In this case, the sixth step of writing the two data selected in the third step to the change history file and the two pieces of data written to the change history file for identifying the field stored as the change point When the change history file is displayed according to a seventh step assigned to the corresponding field and an external instruction, the field to which the identification information is given is displayed in different colors before and after the change. And an eighth step .

In addition, according to one configuration example of the database change point search method of the present invention, if the information does not match in any field as a result of the comparison in the fourth step, The data includes a ninth step of writing a change type indicating a change of data in the change type field of the change history file.
Further, in one configuration example of the database change point searching method of the present invention, in the third step, the same key field as the key field information of the data of the first file stored in the second step is stored. If the prepared data does not exist in the second file stored in the second step, the tenth step of writing the data of the first file into the change history file, and the first step of writing into the change history file And an eleventh step of writing a change type indicating deletion of data in the change type field of the change history file for the data of one file.
Further, in one configuration example of the database change point searching method of the present invention, in the third step, the same key field as the key field information of the data of the second file stored in the second step is stored. If the prepared data does not exist in the first file stored in the second step, the twelfth step of writing the data of the second file into the change history file and the first file written in the change history file And a thirteenth step of writing a change type indicating addition of data in the change type field of the change history file for the data of the second file.

In the database change point search device of the present invention, the first file before change and the second file after change are preset with a plurality of fields to be searched for change points designated from the outside. Reading means for reading the key field; data storage means for storing data of the read field of the first file; and storing data of the read field of the second file; and the key field Data selection means for selecting the same data from the first file data and the second file data stored by the data storage means, and the two data selected by the data selection means, Comparison means for comparing each common field other than the key field, and the result of comparison by this comparison means, If the information does not match in any of the fields, the change point storage means for storing this field as a change point, and if the information does not match in any field as a result of the comparison by the comparison means, the data Write means for writing the two data selected by the selection means to the change history file, and information for identifying the field stored as the change point is assigned to the corresponding fields of the two data written to the change history file Identification information providing means for displaying, and when displaying the change history file in accordance with an instruction from the outside, display means for displaying the field to which the identification information is given in different colors before and after the change. Is.

  Conventionally, when checking the change history of monitoring points, it is necessary to manually compare the first file before the change with the second file after the change and find the difference (change) in the registered contents. As a result, it took a lot of labor, and a human error was caused such that the registered contents remained unchanged. On the other hand, in the present invention, data having the same information in the key field is selected from the data of the first file and the data of the second file, respectively, and these two data are used as common data other than the key field. By making a comparison for each field, it is possible to automatically store only a field with a difference as a change point, so that the confirmation operation can be completed in a much less labor and in a shorter time than in the past. In the present invention, if the information does not match in any field as a result of comparison, the two selected data are written in the change history file, and the information for identifying the field stored as the change point is changed. The two fields written in the history file are assigned to the corresponding fields. As a result, if the present invention is applied to, for example, a change point search of form data of a building monitoring system, it is possible to easily recognize which monitoring point the changed data is, and which of the monitoring points. It is possible to easily recognize whether the field data has been changed. In the present invention, when only the common field of the data of the first file and the data of the second file is extracted and compared, the data is compared as a character string, so the data length before or after the change is Even if they are different, it is possible to reliably determine whether there is a difference, eliminate the conventional human error, and correct the difference and register correctly.

  Also, in the present invention, if the information in any field does not match as a result of the comparison in the fourth step, the data change is made to the change type field of the change history file for the two data written to the change history file. Can be easily recognized that the data of the first file has been changed.

  In the present invention, in the third step, the data having the same key field as the key field information of the data of the first file stored in the second step is stored in the second step stored in the second step. If this file does not exist, the data of the first file is written in the change history file, and the change type indicating the deletion of data in the change type field of the change history file for the data of the first file written in the change history file Can be easily recognized that the data of the first file has been deleted. Therefore, if the present invention is applied to, for example, a change point search of form data in a building monitoring system, it is possible to easily confirm the increase or decrease in the number of monitoring points before and after the change.

  Further, in the present invention, in the third step, the data having the same key field as the key field information of the second file data stored in the second step is stored in the first step stored in the second step. If this file does not exist, the data of the second file is written to the change history file, and the change type indicating the addition of data in the change type field of the change history file for the data of the second file written to the change history file Can be easily recognized that the data of the second file has been added. Therefore, if the present invention is applied to, for example, a change point search of form data in a building monitoring system, it is possible to easily confirm the increase or decrease in the number of monitoring points before and after the change.

[First Embodiment]
Hereinafter, embodiments of the present invention will be described with reference to the drawings. First, a central monitoring device of a building monitoring system that uses form data will be described in order to explain the details of the form data that is the subject of change point search in the present embodiment. FIG. 1 is a block diagram showing one configuration example of a central monitoring device of a building monitoring system according to an embodiment of the present invention.

In FIG. 1, 1-1 is a CPU, 1-2 is a RAM, 1-3 is a ROM, 1-4 is a storage device such as a hard disk device, 1-5 to 1-7 are interface devices (hereinafter referred to as I / F). 1-8 is a display device, 1-9 is a keyboard, and 1-10 is a mouse.
The CPU 1-1 obtains various input information given via the I / Fs 1-5 and 1-7, and operates according to programs stored in the ROM 1-3 and the storage device 1-4 while accessing the RAM 1-2. Then, information is displayed on the display device 1-8 via the I / F 1-6.

The storage device 1-4 stores an electronic form creation program (not shown). This electronic form creation program is provided in a state where it is recorded on a recording medium such as a CD-ROM, and is read from this recording medium and installed in the storage device 1-4.
In the building monitoring system, for example, form data that sets the name and number of the monitoring point, the data type, etc. in order to collect data from the monitoring points of various equipment such as air conditioning equipment, power equipment, crime prevention equipment, and disaster prevention equipment. Are created in advance using an electronic form creation program. In the example of FIG. 1, a database DY is constructed in the storage device 1-4, and a form file FB1 that is a collection of form data is created in the database DY.

  The CPU 1-1 identifies a monitoring point from which data is to be collected based on the form file FB1, collects data from the monitoring point through the I / F 1-5, and stores the collected data in the storage device 1-4. The data is displayed on the display device 1-8 through the I / F 1-6.

  FIG. 2 shows an example of the structure of the form file FB1 stored in the storage device 1-4. The form file FB1 includes data structure information 100 and form data 101. The data structure information 100 indicates the format (data structure) of the form data 101. The data structure information 100 includes a field (column) number 102 and a field attribute 103. According to the definition of the data structure information 100, the form data 101 is composed of N fields, a form number unique to each form data is stored in the number # 1 field, and a line number is stored in the number # 2 field. The point name of the monitoring point is stored in the field of number # 3, the module number is stored in the field of number # 4, and the number of the monitoring point is stored in the field of number #N.

  In the example of FIG. 2, the form file FB1 includes 125 form data with form numbers “001” to “125”. For example, in the form data of form number “001”, the line number is “1”, the point name is “5F air supply fan”, the module number is “21”, and the point number is “10”.

  Next, a general-purpose computer used for searching for changes in the form data will be described. This general-purpose computer is used, for example, by a worker of a building monitoring system development company. FIG. 3 is a block diagram showing one configuration example of the general-purpose computer according to the embodiment of the present invention. In FIG. 3, 2-1 is a CPU, 2-2 is a RAM, 2-3 is a ROM, 2-4 is a storage device such as a hard disk device, 2-5 to 2-7 are I / Fs, and 2-8 is a display. A device, 2-9 is a keyboard, and 2-10 is a mouse.

The CPU 2-1 obtains various input information given via the I / Fs 2-5 and 2-7, and operates in accordance with programs stored in the ROM 2-3 and the storage device 2-4 while accessing the RAM 2-2. Then, information is displayed on the display device 2-8 via the I / F 2-6.
The storage device 2-4 stores a database change point search output program (not shown) as a program specific to the present embodiment. In addition, an electronic form creation program (not shown) is stored in the storage device 2-4. The database change point search output program and the electronic form creation program are provided in a state of being recorded on a recording medium such as a CD-ROM, for example, read from the recording medium, and installed in the storage device 2-4. .

  An operator can create and change a form file using the general-purpose computer as described above. For example, when a design change occurs in a building monitoring system and it is necessary to change a monitoring point, an operator can save a form file FB1 stored in the database DY of the central monitoring device as a recording medium such as a flexible disk or a network. To the database DP in the storage device 2-4. The worker edits the form file FB1 using the electronic form creation program to reflect the contents of the design change, and creates a new form file FB2. FIG. 2 shows a state in which a pre-change form file FB1 is stored in the database DP and a post-change form file FB2 is created. The form file FB2 has the same structure as the pre-change form file FB1.

  After changing the form file, the operator can check the change history of the form file using the database change point search output program of the general-purpose computer. 4 and 5 are flowcharts showing database change point search processing according to this embodiment. The CPU 2-1 of the general-purpose computer performs the processes shown in FIGS. 4 and 5 according to the database change point search output program stored in the storage device 2-4. As a result, the general-purpose computer reads the field and key field to be searched for the change point for each of the pre-change form file and the post-change form file, and reads the pre-change and post-change form files. Data storage means for storing the field data, data selection means for selecting the same data in the key field information from the pre-change form file and the post-change form file, and the two selected form data as the key field Comparison means for comparing each other common field, if the information does not match in any field as a result of the comparison, change point storage means for storing this field as a change point, and information in any field If they do not match, the two selected form data are Writing means for writing to the file, and identification information giving means for giving information (change point identification flag) for identifying the field stored as the change point to the corresponding fields of the two form data written to the change history file It functions as a database change point search device.

  Hereinafter, the processing of FIGS. 4 and 5 will be described. First, the operator operates the keyboard 2-9 and the mouse 2-10 to designate the pre-change form file FB1 and the post-change form file FB2 to be changed, and change point search. The target field is specified by, for example, a field number.

  The CPU 2-1 reads the data structure information of the pre-change form file FB1 stored in the storage device 2-4, identifies the field designated by the operator based on the data structure information, Data is read from the form file FB1. Then, the CPU 2-1 stores the read data in the database DP of the storage device 2-4 as a pre-change form file FB1 'for comparison (step 401 in FIG. 4). An example of the pre-change form file FB1 'is shown in FIG.

  Next, the CPU 2-1 reads the data structure information of the changed form file FB2 stored in the storage device 2-4, identifies the field designated by the operator based on the data structure information, and is designated. The field data is read from the form file FB2. Then, the CPU 2-1 stores the read data in the database DP of the storage device 2-4 as a changed form file FB2 'for comparison (step 402). An example of the post-change form file FB2 'is shown in FIG. Note that the form number of field number # 1 is used unconditionally as necessary field data in steps 401 and 402 since it is used as a sort / comparison key as described later.

Subsequently, the CPU 2-1 stores the pre-change form file FB1 ′ and the post-change form file FB2 ′ in the RAM 1-2 (step 403).
The CPU 2-1 sets the count value n for counting fields to 1, reads the data structure information of the pre-change form file FB 1 ′ stored in the RAM 1-2, and uses the form number of the n = 1st field as a key field. At the same time, the data structure information of the post-change form file FB2 ′ stored in the RAM 1-2 is read, and the form number of the n = 1st field is set as a key field (step 404).

  Then, the CPU 2-1 sorts the data of the pre-change form file FB1 'and the data of the post-change form file FB2' so that the key field values are in ascending order (step 405). The pre-change form file FB1 ′ includes 125 form data whose form numbers are “001” to “125” (FIG. 6), and the post-change form file FB2 ′ has form numbers “001” to “123”, It includes 125 form data “125” and “126” (FIG. 7).

  Next, the CPU 2-1 sets the count value a for counting the form data in the pre-change form file FB1 ′ to A (A is the number of form data in the pre-change form file FB1 ′) (step 406), and the pre-change form file For the a-th form data of FB1 ′, the value of the key field (form number) is read, and the form data having the key field that matches this value is searched in the changed form file FB2 ′ (step 407). Here, it is assumed that the form data of the post-change form file FB2 'obtained as a result of the search is b-th. In the example of FIG. 6, “001” is written as the form number in the key field of the a = 1st form data of the pre-change form file FB1 ′. In the example of FIG. 7, since the form data of the post-change form file FB2 ′ having the key field that matches “001” exists first, b = 1.

Subsequently, the CPU 2-1 selects the a-th form data of the pre-change form file FB 1 ′ and the b-th form data of the post-change form file FB 2 ′, whose key field values match, as comparison target data. (Step 408).
Then, the CPU 2-1 compares the two selected form data for each field having the same number excluding the key field, that is, every n = 2 to Nth field. Specifically, the CPU 2-1 sets n = 2 (step 409), information on the nth field of the ath form data of the pre-change form file FB1 ′, and the bth form of the post-change form file FB2 ′. The information in the nth field of the data is compared (step 410).

  As a result of the comparison, if the information in the nth field matches (NO in step 411), the CPU 2-1 determines whether n = N is satisfied, that is, whether the comparison is completed up to the last field #N. (Step 413), if the count value n has not reached the last field number #N, the count value n is incremented by 1 (step 414) and the process returns to step 410. In this way, the processing of steps 410, 411, 413, and 414 is performed for each count value n.

  On the other hand, if the CPU 2-1 determines in step 411 that the information in the nth field does not match, the mismatch information indicating that there is a mismatch in the information in the nth field of the two selected form data. Are stored in the RAM 2-2, and the a-th form data of the pre-change form file FB1 ′ and the b-th form data of the post-change form file FB2 ′ are written in the change history file FR in the database DP (step 412). . An example of the change history file FR is shown in FIG.

  At this time, the CPU 2-1 creates a data division field in the change history file FR, and if the form data to be written in the change history file FR is the form data of the pre-change form file FB1 ′, the “change” field displays “change”. If it is the form data of the changed form file FB2 ′, “after change” is written in the data classification field. As a result, it is possible to determine whether it is the form data of the pre-change form file FB1 'or the form data of the post-change form file FB2'.

  Further, the CPU 2-1 sets the change point identification flag for the nth field of the two form data written in the change history file FR so that the change point of the form data can be identified. In the example of FIG. 8, a place where the change point identification flag is set is indicated by a pear ground.

  Further, the CPU 2-1 creates a change type field in the change history file FR and writes the change type. For example, in the example of FIG. 8, the line number is “1” in the form data before the change of the form number “0002”, whereas the line number is “1” in the form data after the change of the same form number “0002”. Since it has been changed to “2”, the change type is set to “change”.

  In the comparison in step 410, the data type of the field information is a numeric type or a character string type. However, since the comparison is performed as character string data when performing the comparison, the numeric type or the character string type is used. Regardless of the difference, if there is a difference in the information written in the fields of the two selected form data, the difference can be reliably determined.

  Next, if n = N is established in step 413, the comparison is completed up to the last field #N. If the determination is YES in step 413, the CPU 2-1 stores all field information between the a-th form data of the pre-change form file FB1 ′ and the b-th form data of the post-change form file FB2 ′. It is determined whether or not they match (step 415 in FIG. 5). If the information in all fields match, the form data selected in step 408 and stored in the RAM 2-2 is deleted (step 416).

  If it is determined in step 415 that the information in at least some fields does not match, or if the processing in step 416 is completed, the CPU 2-1 determines whether a = 1 is satisfied, that is, the pre-change form file FB 1 ′. It is determined whether the process has been completed up to the first form data (step 417). If a = 1 is not satisfied, the count value a is decreased by 1 (step 418), and the process returns to step 407.

  In this way, the processing in steps 407 to 418 is performed for each form data of the pre-change form file FB1 '. If a = 1 is satisfied in step 417, the comparison between the form data of the pre-change form file FB1 ′ and the form data of the post-change form file FB2 ′ having the same key field value is completed. become.

  The above process is a process for searching for changes when the change type is “Change”. However, the change type of form data is “Delete” (changed when form data is deleted). And “add” (when the form data exists only in the post-change file FB2 ′ due to the addition of the form data). In order to determine the case where these change types are “deletion” and “addition”, a search is executed in the following flow.

  If a = 1 is established in step 417, the CPU 2-1 does not have any form data having a key field that matches the value of the key field of the form data in the pre-change form file FB1 ′ in the post-change form file FB2 ′. In this case (YES in step 419), the form data of the pre-change form file FB1 ′ is written in the change history file FR in the database DP, and the change type of the form data is set to “delete” (step 420).

  For example, the count value a = 124, and the form number of the key field written in the data structure information is read for the 124th form data of the pre-change form file FB1 '. In the example of FIG. 6, “124” is written as the form number in the key field of the 124th form data, and this “124” is read as the key of the key field. Next, the CPU 2-1 searches for information in the key field of the b-th form data of the changed form file FB2 'that matches the read key. In the example of FIG. 7, the form data having a key field that matches the key read from the form data of the pre-change form file FB1 'does not exist in the post-change form file FB2'.

  As a result, the determination in step 419 is YES, and the CPU 2-1 selects the 124th form data of the pre-change form file FB1 ′, and the change history file FR as shown in FIG. 8 stores the pre-change form file FB1 ′. The 124th form data is written (step 420). At this time, the CPU 2-1 can determine at a glance whether the form data to be written in the change history file FR is data before change or data after change. Here, since the form data written in the change history file FR is the form data of the pre-change form file FB1 ', "before change" is written in the data classification field as shown in FIG.

  Further, the CPU 2-1 can determine at a glance that the form data has been deleted. In the example of FIG. 8, “Delete” is written as the change type in the change type field of the form data written in the change history file FR.

  Further, when a = 1 is established in step 417, the CPU 2-1, the form data having the key field that matches the value of the key field of the form data in the post-change form file FB2 ′ is stored in the pre-change form file FB1 ′. If it does not exist (YES in step 419), the form data of the changed form file FB2 ′ is written in the change history file FR in the database DP, and the change type of the form data is set to “add” (step 420). .

  For example, the count value b for counting the form data of the changed form file FB2 ′ is set to 125, and the form number of the key field written in the data structure information is read for the 125th form data of the changed form file FB2 ′. . In the example of FIG. 7, “126” is written as the form number in the key field of the 125th form data, and this “125” is read as the key of the key field. Next, the CPU 2-1 searches for information in the key field of the a-th form data of the pre-change form file FB1 'that matches the read key. In the example of FIG. 6, the form data having a key field that matches the key read from the form data of the post-change form file FB2 'does not exist in the pre-change form file FB1'.

  As a result, the determination in step 419 is YES, and the CPU 2-1 selects the 125th form data in the post-change form file FB2 ′, and the change log file FR2 ′ in the post-change form file FB2 ′ is selected as shown in FIG. The 125th form data is written (step 420). At this time, the CPU 2-1 can determine at a glance whether the form data to be written in the change history file FR is data before change or data after change. Here, since the form data written in the change history file FR is the form data of the changed form file FB2 ', "after change" is written in the data classification field as shown in FIG.

  Further, the CPU 2-1 can determine at a glance that the form data has been added. In the example of FIG. 8, “addition” is written as the change type in the change type field of the form data written in the change history file FR. In this way, the change history file FR as shown in FIG. 8 is generated in the database DP in the storage device 2-4.

  As described above, in the present embodiment, data having the same key field information is selected from the form data of the pre-change form file FB1 ′ and the form data of the post-change form file FB2 ′, and the two forms are selected. By comparing the data for each common field other than the key field, only the field with the difference is automatically stored as the change point, so it is confirmed with much less labor and shorter time than before. Work can be completed.

  In the present embodiment, if the information does not match in any field as a result of the comparison, the two selected form data are written in the change history file FR, and the field stored as the change point is identified. Information (change point identification flag) is assigned to the corresponding fields of the two form data written in the change history file FR. When the operator operates the keyboard 2-9 and the mouse 2-10 to instruct the CPU 2-1 to display the change history file FR after the database change point search processing shown in FIGS. -1 displays the change history file FR on the display device 2-8 via the I / F 2-6.

  At this time, the CPU 2-1 makes it possible to determine at a glance that there has been a change, for example, by color-displaying the field in which the change point identification flag is set. As a result, the operator can easily recognize which monitoring point the changed form data is, and can easily recognize which field data of the monitoring point has been changed. it can. For example, in the example of FIG. 8, the line number is “1” in the form data before the change of the form number “0002”, whereas the line number is “1” in the form data after the change of the same form number “0002”. It can be easily recognized that it has been changed to “2”.

In the present embodiment, as an application target of the database change point search method of the present invention, the form data used in the building monitoring system is described as an example. However, the present invention is not limited to this. It goes without saying that it can also be applied to databases.
In the present embodiment, every time a change is found for each form data of the pre-change form file FB1 ′ and the post-change form file FB2 ′, the form data is written to the change history file FR. After the change point search is performed on the form data, the mismatched data may be written in the change history file FR.
Further, when the change history file FR shown in FIG. 8 is displayed, the form data before the change is displayed in green, for example, and the form data after the change is displayed in blue, for example, before and after the change. You may display by color.

  The present invention can be applied to a technique for searching for changes in a file stored in a database.

It is a block diagram which shows one structural example of the central monitoring apparatus of the building monitoring system which concerns on embodiment of this invention. It is a figure which shows the structure of the form file in embodiment of this invention. It is a block diagram which shows one structural example of the general purpose computer which concerns on embodiment of this invention. It is a flowchart which shows the database change point search process of the general purpose computer of FIG. It is a flowchart which shows the database change point search process of the general purpose computer of FIG. It is a figure which shows an example of the pre-change form file used as the object of a change point search in embodiment of this invention. It is a figure which shows an example of the after-change form file used as the object of a change point search in embodiment of this invention. It is a figure which shows an example of the change history file obtained as a result of the change point search in embodiment of this invention.

Explanation of symbols

1-1, 2 ... CPU, 1-2, 2-2 ... RAM, 1-3, 2-3 ... ROM, 1-4, 2-4 ... storage device, 1-5 to 1-7, 2 -5 to 2-7 ... interface device, 1-8, 2-8 ... display device, 1-9, 2-9 ... keyboard, 1-10, 2-10 ... mouse.

Claims (5)

A first step of reading a plurality of fields to be searched for change points designated externally and a preset key field for each of the first file before the change and the second file after the change;
Storing the read field data of the first file and storing the read field data of the second file;
A third step of selecting data having the same information in the key field from data of the first file and data of the second file stored in the second step;
A fourth step of comparing the two data selected in the third step for each common field other than the key field;
As a result of the comparison in the fourth step, if the information does not match in any field, the fifth step stores this field as a change point;
As a result of the comparison in the fourth step, if the information does not match in any field, the sixth step writes the two data selected in the third step to the change history file;
A seventh step of assigning information for identifying the field stored as the change point to the corresponding fields of the two data written in the change history file ;
When displaying the change history file in response to an instruction from the outside, an eighth step is provided in which the field to which the information for identification is added is color-coded before and after the change. Database change point search method. In the database change point search method according to claim 1,
Further, as a result of the comparison in the fourth step, if the information does not match in any field, the two types of data written in the change history file are changed in the change type field of the change history file. A database change point search method comprising a ninth step of writing a change type to be expressed. In the database change point search method according to claim 1,
Further, in the third step, data having the same key field as the key field information of the first file data stored in the second step is stored in the second step stored in the second step. A tenth step of writing data of the first file to the change history file if it does not exist in the file;
A database change point search method comprising: an eleventh step of writing a change type representing data deletion into the change type field of the change history file for the data of the first file written to the change history file . In the database change point search method according to claim 1,
Further, in the third step, the data having the same key field as the key field information of the data of the second file stored in the second step is stored in the first step stored in the second step. A twelfth step of writing the data of the second file to the change history file if it does not exist in the file;
A database change point search method comprising: a thirteenth step of writing a change type indicating addition of data in the change type field of the change history file for the data of the second file written to the change history file . Reading means for reading a plurality of fields to be searched for change points designated from the outside and a preset key field for each of the first file before the change and the second file after the change,
Data storage means for storing the read field data of the first file and storing the read field data of the second file;
Data selection means for selecting data having the same information in the key field from data of the first file and data of the second file stored by the data storage means;
Comparing means for comparing two data selected by the data selecting means for each common field other than the key field;
As a result of comparison by the comparison means, if the information does not match in any field, a change point storage means for storing this field as a change point;
As a result of comparison by the comparison means, if the information does not match in any field, the writing means for writing the two data selected by the data selection means to the change history file;
Identification information giving means for giving information for identifying the field stored as the change point to the corresponding fields of the two data written in the change history file ;
A database change characterized by having a display means for displaying the field to which the information for identification is given in color before and after the change when displaying the change history file according to an instruction from the outside Point search device.

Images