JP2006146470A - Database updating method, database updating program and program recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a database updating method capable of reliably and efficiently updating a database. <P>SOLUTION: This method for updating a database in which a plurality of records including a plurality of attribute regions for storing data are recorded comprises: a first process for deciding predetermined consistency between each of newly prepared new update records being the target of update and a record corresponding to the new update record in the database; and a second process for updating the corresponding record in the database based on the new update record for the record whose predetermined consistency is decided to be satisfied from the decision result of the first process. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an exposure apparatus used in a lithography process for manufacturing an electronic device (hereinafter simply referred to as an electronic device) such as a semiconductor element, a liquid crystal display element, an imaging element such as a CCD, a plasma display element, and a thin film magnetic head. The present invention relates to a database update method for managing information related to parts used in the design and manufacture of machine products, a program for the same, and a recording medium for the program.

  For example, when designing a mechanical product such as an exposure apparatus, a CAD system linked to processing such as ordering of parts to be used and production management in a production line is usually used. In such a CAD system, information such as parts recommended for use in the company or permitted to be used or parts already used in the database is stored in a database. The design is performed while referring to the component information.

  In such a database system, it is very important to manage and maintain the stored data. For example, since such a database system is simultaneously accessed from a plurality of terminal devices, it is difficult to set a timing for updating data. In addition, when a plurality of workers perform maintenance or the like, it may be difficult to maintain the reliability of the data contents. In addition, such updating and management of the database may be based on commands that are complicated and difficult to understand, and there is a problem that only some specialized workers may be able to work.

Therefore, for example, by providing an interactive operation tool etc., even an operator who does not have sufficient knowledge of the database or is unfamiliar with the input operation using the keyboard etc. can easily input, search, update, and delete the database. An efficient and highly reliable database management system that can perform operations such as the above has been proposed (see, for example, Patent Document 1).
JP-A-7-141238

  However, even in such a database management system, how to ensure the reliability of the accumulated data and how to update the accumulated data with high reliability is not sufficient. In this respect, an efficient and reliable method is demanded.

  Specifically, for example, when checking the reliability of the contents of data stored in a database, it may be possible for an operator or the like to check one by one if it is a small number of tens to hundreds. However, when it becomes a large number of thousands or more, it takes time and accuracy is also a problem. Some data cannot be confirmed as valid / invalid (error) at first glance. In other words, even if an operator infers that it is a meaningless invalid symbol, it may actually contain very important and meaningful data, and the contents of each individual data are well known. It may be necessary to check with the person in charge. In addition, when changing or updating part data, rewriting data used in manufacturing as proven data with incorrect data may cause significant damage in practice. Even carefulness is required.

The present invention has been made in view of such problems, and it is an object of the present invention to provide a database update method capable of updating a database with high reliability and efficiency.
Another object of the present invention is to provide a program and a program recording medium for realizing such a database update method with a computer.

  In order to solve the above problems, a database update method according to the present invention is a database update method in which a plurality of records each including a plurality of attribute areas in which data can be stored is recorded. For each new update record, the first step for determining a predetermined consistency between the new update record and the record corresponding to the new update record in the database, and the determination result of the first step A second step of updating the corresponding record in the database on the basis of the new update record for the record determined to satisfy the predetermined consistency.

  Further, the database update program according to the present invention is a database update program in which a plurality of records including a plurality of attribute areas each capable of storing data is recorded, and each newly updated record to be updated is newly created. And a first function for determining a predetermined consistency between the new update record and a record corresponding to the new update record in the database, and a result of determination by the first function, The record determined to satisfy the consistency has a second function of updating the corresponding record in the database based on the new update record.

  The recording medium on which the database update program according to the present invention is recorded is a program recording medium on which the above-described database update program is recorded in a readable form.

ADVANTAGE OF THE INVENTION According to this invention, the database update method which can update a database reliably and efficiently can be provided.
Further, it is possible to provide a program and a program recording medium for realizing such a database update method with a computer.

A database update system according to an embodiment of the present invention will be described with reference to FIGS.
In the present embodiment, for example, a system that updates information stored in a parts database that stores information on parts used in various machine products and electrical products including a manufacturing machine such as an exposure apparatus will be described. . This parts database is used in a CAD system used when designing those products, a production management system used when actually manufacturing those products, and the like.

First, an overview of the database update system and the parts database will be described.
FIG. 1 is a diagram illustrating a configuration of a database update system 10 according to the present embodiment.
The database update system 10 includes a processing system (processing process) related to three-stage data update, that is, a check system 11, a pouring system 12, and a forced writing system 13.

  In the database update system 10, first, in the check system 11, a record to be updated (new update record) recorded in the input file 31 and a corresponding record (PDB record) already accumulated in the parts database (PDB) 20. Check consistency with. The check result is output as a check result file 32 in a state that the operator can easily confirm. Based on the check result, the operator confirms and reviews each record in the input file 31 and the parts database 20, and corrects them as necessary.

  Next, the parts database 20 is actually updated in the pouring system 12. The flow-in system 12 checks the consistency between the newly updated record recorded in the reviewed input file 33 and the corresponding record in the parts database 20, and if a match is found, the new updated record indicates that the parts database 20 Update the corresponding record. If no match is found, the newly updated record, the corresponding PDB record, and the check result are output to an inconsistent record file 34 as an output file. The operator confirms and reviews each record in the input file 33 and the parts database 20 again based on the inconsistent record file 34.

Next, the forced writing system 13 checks which of the newly updated record and the PDB record is more likely to be an appropriate record for the inconsistent record recorded in the inconsistent record file 34. As a result, when there is a high possibility that the new update record is more appropriate, the corresponding record in the parts database 20 is updated based on the new update record. If there is a low possibility that the new update record is more appropriate, the new update record, the corresponding PDB record, and the check result are output to the forced write result file 35 as an output file.
The specific processing flow and the input / output files 31 to 35 in each processing step (processing system) will be described in detail later.

  In the parts database 20, various data related to parts are recorded and stored as one record for each part. Each record includes, for example, a drawing number, a model name, a manufacturer code, an update date, a comment, a rating, a drawing remark, a classification DIR, a symbol name, a temporary name, a sheet DIR, a data sheet, attributes such as a rated voltage, a library (symbol and PDF) ) And library code (symbols and PDF) and the like (see FIG. 4. FIG. 4 is a diagram showing an example of a PDB record listed from the component database 20, which will be described later). The component database 20 is a database in which records having attribute areas for recording data of these data items are stored for each component.

In the parts database 20, valid data is not necessarily recorded for all attribute areas of each component record, that is, for all data items of each component record. Effective data is recorded in necessary items as appropriate according to the part. At this time, valid data is recorded for valid items, and NULL is recorded for invalid items.
Further, each record is recorded in the parts database 20 so as to be searched using “drawing number” as a key. Therefore, the data of the figure number is always recorded as valid data in each record.

Next, each processing system (processing process) of the database update system 10 will be described in detail.
First, the check system 11 will be described with reference to FIGS.
FIG. 2 is a diagram illustrating a data flow according to the check system 11.
As shown in FIG. 2, the check system 11 checks the consistency between the newly updated record recorded in the input file 31 and the corresponding record in the component database 20, and outputs the check result as a check result file 32. The check system 11 searches the parts database 20 based on the new update record of the input file 31, and lists the corresponding PDB records. And the consistency of these records is confirmed by comparing each data of a new update record and a PDB record.

An example of the input file 31 is shown in FIG.
In FIG. 3, a series of data in one line indicates data of one part, and this constitutes one record (new update record) of the input file 31. In the input file 31 illustrated in FIG. 3, four new update records corresponding to the four parts of the diagram number “4S110-041” to the diagram number “4S110-066” are illustrated. For ease of explanation, as shown in FIG. 11-No. Reference numeral 14 is attached and referred to in the following description.
The data items of each record of the input file 31 are substantially the same as the data items of the record of the parts database 20 (FIG. 4) described above.
In FIG. 3, the records of the input file 31 are shown in a table format. However, the actual input file 31 is a CSV format file in which one record (data of one part) is described for each line. is there.

FIG. 4 shows PDB records listed from the component database 20 by the check system 11 in correspondence with such a new update record of the input file 31.
Also in FIG. 4, a series of data in one row shows data of one part, and this corresponds to one record (PDB record) of the parts database 20. The PDB record illustrated in FIG. 4 is a record of four parts of the figure numbers “4S110-041” to “4S110-066” corresponding to the new update record of the input file 31 shown in FIG. For ease of explanation, as shown in FIG. 21-No. Reference numeral 24 is attached and referred to in the following description.

  Since the record of the input file 31 is created according to the record of the parts database 20, the data items of the PDB record and the new update record are almost the same. However, there are differences in the format of some data. In the record of the component database 20, as shown in FIG. 4, in the data item indicating the attribute such as the rated current, the data is expressed by a significant number and a number (exponential number) of the exponent part.

Next, processing in the check system 11 will be described in detail with reference to FIGS.
5 and 6 are diagrams illustrating a specific processing flow of the check system 11.
In the check system 11, when the file name of the input file 31 is input (step S11), the new update target record (new update record) recorded in the input file 31 is read in record units (step S12).
From the input file 31 illustrated in FIG. Eleven new update records are read.

  When a new update record is read from the input file 31 (step S12 (FIG. 5)), the parts database 20 is searched using the data of “number” described in the new update record as a key. A record corresponding to the new update record is read (step S14). No. 11, the data “4S110-041” is recorded as the data of “figure number”, so that the record of the same figure number is stored from the parts database 20 using this figure number as a key. read out. As a result, the record read out is recorded as No. 1 shown in FIG. 21 PDB records.

  When the corresponding record is read from the parts database 20, the new update record read from the input file 31 (No. 11 record shown in FIG. 3) and the corresponding PDB record (No. 21 record shown in FIG. 4). Is checked for consistency (step S15).

  In the consistency check between records, the data consistency of each data item included in the record is checked, and when there is no inconsistent data, it is determined that the data between the records is consistent. In addition, this consistency check includes five data items to be checked: (1) basic data, (2) other rated data, (3) attribute data, (4) library data, and (5) library code data. The data items are classified into types, and the consistency is determined for each type of data. The consistency determination result for each type is output to the check result file 32 (see FIG. 1 or 2) in the form of a flag.

(1) In the comparison of basic data, the data of each item of drawing number, model name, manufacturer code, update date and comment is compared.
(2) In the comparison of rating and other data, the data of each item of rating and remarks on drawings are compared.
(3) In attribute data comparison, attribute values (data) indicating functions and characteristics of the component such as rated voltage, rated current, rated power, resistance value, and number of poles are compared.
(4) In the comparison of library data, the data of each item of classification DIR, symbol name, sheet DIR, and data sheet is compared.
In the comparison of (5) library code data, data of each item of the symbol temporary name, library (symbol, PDF), and library code (symbol, PDF) is compared.

  The consistency between the data (new update data) included in the new update record and the data (PDB data) included in the record of the parts database 20 is determined when the contents of the new update data and the PDB data are equal, and the PDB data. When no valid data is recorded (when the PDB data is NULL), it is determined that the new update data and the PDB data are consistent. That is, as shown in FIG. 7, when the content of the new update data is “A” and the content of the corresponding PDB data is also “A”, the content of the new update data is “B” and the corresponding PDB data If the content of the PDB data also matches “B”, and the content of the PDB data is NULL, the new update data and the PDB data are assumed to be consistent. At this time, a flag “0” indicating that matching is achieved is set as a determination result.

  In addition, when the PDB data is valid data and is different from the new update data (when the values of the new update data and the PDB data are different, and when the PDB data is not NULL but the new update data is NULL), It is determined that the new update data and the PDB data are not consistent (inconsistent). At this time, a flag “1” indicating that the matching is not achieved is set as a determination result.

FIG. 6 shows the flow of processing for checking consistency between records (step S15 (FIG. 5)). A specific example of the process of checking consistency between records is shown in FIG.
Hereinafter, processing for checking consistency between records will be described with reference to FIGS. 6 and 8.

In the process of checking consistency between records, first, the type of data for checking consistency is set (step S21). In the present embodiment, (1) basic data to (5) library code data are set in order, and (1) basic data is set first.
8A and 8B show a part of the record of the input file 31 shown in FIG. 3 and the parts database 20 shown in FIG. 4 and whose data items are classified into (1) basic data. An excerpt is shown in (B).

  Next, data to be compared and included in the set type is selected from the new update data and the corresponding PDB data (step S22). For example, (1) “Figure No.” data, which is the first data item in the basic data, is selected from both the new update record and the PDB record. No. shown in FIG. In the new update record of No. 11, data “4S110-041” is selected (extracted), and No. 1 shown in FIG. In the 21 PDB records, data “4S110-041” is selected (extracted).

Then, the diagram number data of the selected new update data is compared with the diagram number data of the PDB data, and it is detected whether these data are equal or whether the PDB data is NULL ( Step S23). As a result, if the new update data and the PDB data are equal, or if the PDB data is NULL, it is determined that the new update data and the PDB data are consistent, and a determination flag “0” indicating that fact is set. (Step S24). In addition, if the new update data is different from the PDB data, or if the PDB data is not NULL but the new update data is NULL, it is indicated that these data are not consistent. The flag “1” is set (step S25). Note that the discrimination flag as the result of comparison and collation is stored (set) in, for example, a memory or the like in the arithmetic processing unit that performs the consistency check process.
No. shown in FIG. 11 and the No. shown in FIG. In the 21 PDB records, since the “diagram number” data is “4S110-041” and are equal to each other, it is determined that they are consistent (step S23), and 11-21 in FIG. 8C. As shown in the “drawing number” column for the record, the discrimination flag “0” is set as the discrimination result.

(1) When the data consistency determination for the first data item (“drawing number”) in the basic data is completed, the process returns to step S22 (FIG. 6) (step S26), and the data of the next data item is stored. select. (1) In the comparison of basic data, the data of “type name” is next selected from both the new update record and the PDB record.
Then, the above-described determination in step S23 is performed on the selected data, and a determination flag is set (step S24 or step S25).
As described above, the processing of step S22 to step S25 is performed as follows. (1) The data type is classified into the basic data “Figure number”, “Model name”, “Manufacturer code”, “Update date” and “ Each data item of “comment” is performed in order.

  At this time, for example, the data of “maker code” is No. The data of “Manufacturer code” of the new update record of No. 11 is “123”. The data of “maker code” of 21 PDB records is “114”, which are different. Therefore, this difference is detected in step S23, and as shown in FIG. 8C, a determination flag “1” indicating that the data of “maker code” in these records is inconsistent is set (step S25). ).

  When the consistency determination processing in steps S22 to S25 is completed for all data included in the type of data to be compared (step S26), the new update record and the PDB for the entire data of that type are then received. The consistency with the record is determined (step S27). Here, when all of the data included in the data type is consistent data, it is assumed that the data type is consistent as a whole. If even one inconsistent data exists among the data types, it is determined that the data types are not consistent.

  More specifically, the consistency determination process (steps S22 to S25) up to the data item “update date” is performed (1) When all the comparisons of data classified as basic data are completed (step S26). In step S27, (1) the consistency of the entire data classified as basic data is determined. As shown in FIG. No. 11 new update record and No. Although the data of “Figure number” and “Type name” are consistent with the 21 PDB records (the discrimination flag is “0”), “Manufacturer code”, “Update date” and “Comment” "Is not consistent (the discrimination flag is" 1 "). Therefore, (1) For data classified as basic data, no. No. 11 new update record and No. It is determined that the data contents are inconsistent with the 21 PDB records, and a flag “1” to that effect is set as shown in FIG.

  When consistency is determined for the type of data in this way, it is further checked whether or not there is a type of data subject to consistency check (step S28), and if it exists, the process returns to step S21. Thus, the next data type is set as the data type of the consistency detection target. Then, the processing of step S22 to step S26 is repeated to check the consistency of all data included in the data type (step S22 to step S26), and based on the check result, the data The consistency of the type as a whole is determined (step S27).

By repeating such processing, all the five types of data (1) basic data, (2) other rated data, (3) attribute data, (4) library data, and (5) library code are described. Consistency is determined for each data type.
No. 1 shown in FIG. 11 and the No. shown in FIG. With respect to the 21 PDB records, as shown in FIG. 8E, the consistency determination result for each data type is detected.

  When the consistency determination processing in steps S21 to S27 is completed for all types of data included in each record (step S28), the consistency between the new update record and the PDB record is then performed. Is determined (step S29). Here, in all the consistency determinations performed for each data type, when the data types are consistent, the new update record and the PDB record are consistent as a whole. Shall. If even one type of inconsistent data exists, it is determined that there is no consistency between the new update record and the PDB record.

No. 1 shown in FIG. 11 and the No. shown in FIG. As shown in FIG. 8E, there are four types of (1) basic data, (2) other rated data, (3) attribute data, and (5) library code data. The result is inconsistency in data (determination flag is “1”), and (4) it is determined that only library data is consistent. Therefore, it is determined that these records are not consistent.
The consistency between records is checked by the above processing.

  Returning to FIG. 5, when the check system 11 checks the consistency between records by such processing (step S15), the result is output to the check result file 32 together with the new update record and the PDB record.

The format of the check result file 32 is shown in FIG.
In the check result file 32, as shown in FIG. 9, a series of data in one row is information (result record) for one component. Therefore, the file illustrated in FIG. 9 shows four check result records. For ease of explanation, each result record has a No. 31-No. The number 34 is attached. These four result records are the No. shown in FIG. 11-No. 14 and four new update records and the No. shown in FIG. 21-No. This record is a result of checking the consistency with 24 PDB records.
In FIG. 9, the records of the check result file 32 are shown in a table format, but the actual file is a CSV format file in which one result record is described for each line.

Each result record of the check result file 32 shown in FIG. 9 is information including a new update record, a PDB record, and a check result. Each result record has the same data items as the record of the input file 31 shown in FIG. 3 and the record of the parts database 20 shown in FIG. 4, and each data item corresponds to a newly updated record whose consistency has been checked. The data item data and the corresponding data item data of the PDB record are arranged side by side. In FIG. 9, the contents of the fields in which the contents of the data items (for example, “figure number”, “type name”, etc.) are clearly shown are the data of the new update record, and the data item on the right side of the page is “DB”. The contents of the column described as “” are the data of the PDB record.
In FIG. 9, the “execution date” data item is described. This is only in the result file (inconsistent record file 34) as an output file of the pouring system 12 described later with reference to FIG. 9. It is an item provided. It is not described in the check result file 32 or data is described in NULL.

  Further, in the check result file 32, between attribute data (record portion shown in the third row in FIG. 9) and library and library code data (record portion shown in the fifth row (bottom row) in FIG. 9) ( In FIG. 9, the consistency determination flag of the check result shown in FIG. The consistency determination flag starts after the data item whose data content is the identifier “#”, and the determination flag detected for each data type ((1) basic data to (5) library code data) is described in order. Is done.

When the result record is written in such a check result file 32 (step S16 (FIG. 5)), the process returns to step S12, the next new update record is read, and if there is a new update record, the process proceeds from step S14 to step S16. Repeat the process.
For example, for the input file 31 shown in FIG. 12-No. 14 new update records are read, respectively, and in step S14, No. 14 shown in FIG. 22-No. 24 PDB records are read from the parts database 20. Then, the consistency between corresponding records is detected by performing the consistency check process as shown in FIG. 6 (step S15 (FIG. 5)), and as shown in FIG. 32-No. 34 result records are sequentially output to the check result file 32.
Then, when there is no new update record to be newly read from the input file 31 (step S13), the processing of the check system 11 is ended (step S17).

  By such processing of the check system 11, for example, consistency between the input file 31 illustrated in FIG. 3 and each record of the component database 20 illustrated in FIG. 4 is detected, and a check result file 32 as illustrated in FIG. can get.

Thus, in the check system 11, based on the input file 31 in which a record to be newly updated is recorded, a corresponding record in the component DB 20 is searched and a data item is listed, and between those records Check consistency.
Therefore, for example, the operator refers to the record of the check result file 32, detects the type of data or the data item of which the determination flag is “1” from the description of the determination flag, and the original new update record The PDB record data (input data, PDB data) is reviewed to determine which data is inappropriate.
If the input file 31 is inappropriate, the data content is changed and a new input file 33 is created.

For example, in the check result file 32 shown in FIG. The discrimination flag for “Rating Other” type data of 33 result records is “1” (inconsistent). Therefore, no. 13 new update records and No. 13 When the data contents of “Rating” and “Remarks on Drawing” of 23 PDB records are checked from FIG. 9 or FIG. 3 and FIG. 4, “470Ω... However, nothing is described in the new update record. Also, in the “Remarks for Drawing Description” column, nothing is described in the new update record even though “DIP” is described in the PDB record, and it is detected that an inconsistent state has occurred. it can.
By such a method, the operator or the like examines which state is appropriate, and corrects the corresponding new update record or the parts database 20 as necessary.
In this check system 11, the parts database 20 is not updated.

Next, each process related to the pouring system 12 of the database update system 10 shown in FIG. 1 will be described with reference to FIGS. 10 and 11.
As shown in FIG. 10, the flow system 12 confirms the consistency between the new input file 33 in which inappropriate data is corrected by the check system 11 and the parts database 20, and matches the input record (new update). For the (record), the parts database 20 is updated based on this. Also, for records that could not be matched, the check result is output as a mismatched record file 34.

The flow of processing of the pouring system 12 is shown in FIG.
In the flow system 12, the process from reading the corresponding PDB record from the parts database 20 based on the new update record of the input file 33 and checking the consistency thereof is performed in steps S11 to S15 of the check system 11 described above. This processing is the same as the processing (see FIG. 5).
That is, when the file name of the input file 33 is input (step S31), the new update target record (new update record) recorded in the input file 33 is read in record units (step S32). The file format of the input file 33 is the same as that of the input file 31 shown in FIG.
When a new update record is read from the input file 33 (step S32), a record corresponding to the new update target record is read from the component database 20.

When the corresponding record is read from the component database 20, the consistency between the newly updated record read from the input file 33 and the record read from the corresponding component database 20 is checked (step S35). This consistency check process is performed by the method described above with reference to FIGS.
As a result of the consistency check in step S35, when the new update record (input record) and the PDB record are matched (step S36), the contents of the new update record (input record) indicate the corresponding in the parts database 20. Data is updated (step S37).

If the new update record and the PDB record cannot be matched (step S36), the consistency check process (the process shown in FIG. 6) performed in the new update record, the PDB record, and step S35. The result is output to the inconsistent record file 34 (step S38).
The format of the inconsistent record file 34 is substantially the same as the format of the check result file 32 described above with reference to FIG. However, in the inconsistent record file 34, information on the date on which the pouring system 12 was executed, that is, information on the date on which the inconsistent record file 34 was created is stored in the item “execution date” in each result record. Keep it. This information is referred to by the forced writing system 13 described later.

As a result of the processing of step S32 to step S38, among the newly updated records described in the input file 33, with respect to the appropriate data, the content of the parts database 20 is updated thereby. The information is output to the result file (inconsistent record file 34) in the CVS format.
Further, when there is no new update record to be read from the input file 33 in step S32, a series of processes of the pouring system 12 is ended (step S39).

  As described above, in the flow-in system 12, the corresponding record in the parts database 20 is searched based on the input file 33 in which the record to be newly updated is recorded, the data items are listed, and the records between these records are also recorded. Check consistency. For the data that is consistent, the component database 20 is updated thereby, and the data that is not consistent is output to the inconsistent record file 34.

  In such a pouring system 12, the operator confirms the record output to the inconsistent record file 34 as the data content is inconsistent, and checks whether the data content is appropriate. If there is a record that seems appropriate against the contents of the parts database 20, it is selected as an input record for the next-stage forced writing system 13. Then, the inconsistent record file 34 in which such a selected record is recorded is provided to the forced writing system 13 as an input file.

Next, each process related to the forced write system 13 of the database update system 10 shown in FIG. 1 will be described with reference to FIGS. 12 and 13.
As shown in FIG. 12, the forced writing system 13 updates the records that are determined to be appropriate for updating the parts database 20 by the operator while the data is inappropriate by the flow system 12, and the corresponding records in the parts database 20 are updated. Compare days. If the record in the inconsistent record file 34 is newer and the dates are the same, it is considered that the record in the inconsistent record file 34 is likely to be an appropriate record. Update the corresponding record.
If the record in the inconsistent record file 34 is older, the record in the inconsistent record file 34 is considered to be less likely to be appropriate, and the parts database 20 is not updated by that record. Output to the forced write result file 35.

The flow of processing of the forced writing system 13 is shown in FIG.
In the forced writing system 13, an inconsistent record file 34 whose format is illustrated in FIG. 9 is used as an input file.
When the file name of the inconsistent record file 34, which is an input file, is input (step S51), the forced writing system 13 sequentially reads the records recorded in the inconsistent record file 34 in record units (step S52).

  When the forcible update target record can be read from the inconsistent record file 34 (step S53), the record corresponding to the new update target record is read from the component database 20 (step S54).

  Next, the update date between these forcible update target records and the record (PDB record) read from the corresponding component database 20 is compared (step S55). The date for comparison is the date when the inconsistent record file 34 described as the data item “execution date” is generated in each record of the inconsistent record file 34 for the record to be forcibly updated (more precisely, The date when the flow system 12 that generated the inconsistent record file 34 was executed) (see FIG. 9). Further, the PDB record is information described as a data item “update date” in the PDB record (see FIG. 4 or FIG. 9).

As a result of the comparison in step S55, when the update date of the forcible update target record is newer (step S56), the discrimination flag “0” is set (step S57), and the forcible update target record (input) The corresponding record in the parts database 20 is updated with the new update record in the record (step S58).
If the update date of the corresponding record in the parts database 20 is newer (step S56), the discrimination flag “1” is set (step S59), the forcible update target record, the corresponding record in the parts database 20 ( The PDB record) and the check result flag are output to the forced write result file 35 (see FIG. 1 or 12) (step S60).

  As a result of step S52 to step S60, among the records to be forcibly updated described in the inconsistent record file 34, for the record whose update date is newer than or the same as the corresponding record in the component database 20, the contents of the component database 20 are thereby obtained. Is updated. Further, for a record with a newer update date in the parts database 20, the information is output to the forced write result file 35 together with the record contents in the parts database 20.

  When the update of the parts database 20 (step S58) or the output of the result file (step S59) is completed, the process returns to step S52 and the next information recorded in the inconsistent record file 34 as the input file is read in record units. . When the next new update target record can be read (step S53), the PDB record corresponding to the new update target record is read (step S54), and the processes of steps S55 to S60 are repeated. In step S52, when there is no record to be read (step S53), the series of processes in the forced writing system 13 is ended (step S61).

  As described above, the forced writing system 13 searches the corresponding records in the parts database 20 based on the inconsistent record file 34 in which the records to be forcibly updated are recorded, lists the data items, Check update date between records. For the record with the newest update date in the input file data, the component database 20 is updated accordingly.

Therefore, the operator can correct the data content of the parts database 20 by using the forced writing system 13. That is, when the content of the record in the parts database 20 is wrong or it is desired to change to the latest information, the forced writing system 13 can correct the data.
On the other hand, in the database update system 10, the correction of the record (PDB record) in the component database 20 by the forced writing system 13 is performed by checking the inconsistency between the new update record to be corrected and the record in the component database 20. And it becomes possible after confirming a plurality of times by the pouring system 12. Therefore, the record of the parts database 20 is not easily changed.
As a result, the reliable parts database 20 can be constructed, and the reliable parts database 20 can be updated.

  In addition, this Embodiment was described in order to make an understanding of this invention easy, and does not limit this invention at all. Each element disclosed in the present embodiment includes all design changes and equivalents belonging to the technical scope of the present invention, and various suitable modifications are possible.

FIG. 1 is a diagram showing a configuration of a database update system according to an embodiment of the present invention. FIG. 2 is a diagram for explaining a check system of the database update system shown in FIG. FIG. 3 is a diagram for explaining the data format of the input file of the database update system shown in FIG. FIG. 4 is a diagram for explaining records recorded in the parts database of the database update system shown in FIG. FIG. 5 is a flowchart showing a flow of processing of the check system shown in FIG. FIG. 6 is a flowchart showing a flow of processing for checking consistency between records. FIG. 7 is a diagram for explaining a flag indicating a consistency check result. FIG. 8 is a diagram for explaining a specific example of the consistency check process. FIG. 9 is a diagram for explaining the data format of an output file such as a check result file of the database update system shown in FIG. FIG. 10 is a diagram for explaining the flow-in system of the database update system shown in FIG. FIG. 11 is a flowchart showing a flow of processing of the pouring system shown in FIG. FIG. 12 is a diagram for explaining a forced write system of the database update system shown in FIG. FIG. 13 is a flowchart showing the flow of processing of the forced writing system shown in FIG. It is a figure which shows the structure of the alignment system of exposure apparatus.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Database update system 11 ... Check system 12 ... Flow-in system 13 ... Forced writing system 20 ... Parts database 31-35 ... Input-output file

Claims (12)

A method for updating a database in which a plurality of records including a plurality of attribute areas each capable of storing data are recorded,
A first step for determining a predetermined consistency between the new update record and a record corresponding to the new update record in the database for each new update record newly created and updated;
A second step of updating the corresponding record in the database based on the new update record for a record determined to satisfy the predetermined consistency from the determination result of the first step. A database update method characterized by the above.   In the first step, among the data in the plurality of attribute areas included in the new update record and the data in the plurality of attribute areas included in the corresponding record, between the two in a predetermined attribute area 2. The database update method according to claim 1, wherein when the data matches, it is determined that the predetermined consistency is satisfied between the records.   In the first step, when the data in the plurality of attribute areas included in the new update record and the data in the plurality of attribute areas included in the corresponding record all match, or the corresponding 3. The database according to claim 2, wherein when at least some of the attribute areas included in the record are in a predetermined state, the records are determined to satisfy the predetermined consistency. 4. Update method.   The database update method according to claim 3, wherein the predetermined state includes a state in which the attribute area is NULL. In the first step, for the new update record determined not to satisfy the predetermined consistency, a third determination is made as to whether the new update record is appropriate for updating the corresponding record in the database. Process,
The record determined to be appropriate in the third step further includes a fourth step of forcibly updating the corresponding record in the database based on the new update record. The database update method according to any one of claims 1 to 4. For the record determined to be inappropriate in the third step, the record further includes a fifth step of correcting data of at least a part of the attribute area of the new update record,
6. The database update method according to claim 5, wherein the processing from the first step is repeatedly executed on the record modified in the fifth step.   Before updating the record in the database based on the newly created record, the creation time of the newly updated record is compared with the update time of the corresponding record in the database, and the time is substantially The database update method according to claim 1, wherein the update is performed based on the new update record when the creation time is newer or the creation time is newer.   For the new update record determined not to satisfy the predetermined consistency in the first step, at least the consistency of the data of the new update record and the corresponding record in the database could not be obtained. The database update method according to any one of claims 1 to 7, wherein the data in the attribute area is output in a form that is specified. A database update program that records a plurality of records including a plurality of attribute areas each capable of storing data,
A first function for determining a predetermined consistency between the new update record and a record corresponding to the new update record in the database for each new update record newly created and updated;
A second function for updating the corresponding record in the database based on the new update record for a record determined to satisfy the predetermined consistency from the determination result in the first function; A database update program characterized by that. A database update program that records a plurality of records having a plurality of data,
A function for detecting the consistency between the new update record and the record of the database corresponding to the record for each new update record newly created and updated;
As a result of the detection of consistency, a function for updating the corresponding record of the database based on the new update record for a consistent record;
A function of outputting the data of the newly updated record and the corresponding record of the database in a form in which at least the inconsistent data is clearly indicated for the inconsistent record as a result of the consistency detection; Database update program to be executed by computer. A database update program that records a plurality of records having a plurality of data,
For each new update record newly created and subject to update, the input time of the new update record is compared with the update time of the corresponding record in the database, and the new update record A function of detecting whether or not a condition that the input time is newer is satisfied,
A function that updates the corresponding record in the database based on the new update record for the record that satisfies the condition;
A database update program for causing a computer to execute a function of outputting information related to detection of the condition for a record that does not satisfy the condition.   A program recording medium in which the database update program according to any one of claims 9 to 11 is recorded in a readable form.

Images