JPH08106473A - Database management system - Google Patents

Abstract

(57) [Summary] [Purpose] To be able to record all the editing work performed by multiple users, and to enable the integration of editing work performed by multiple users. [Structure] When a query is made to the database, DBMS2
Notifies the "version number" and "contents" of the inquired database. When editing data and registering it in database 3, application 1 uses the database name and version,
Request the registration with the contents. The DBMS 2 newly secures a data area, attaches a new version number, performs registration processing, and notifies the processing result. When updating the database, a tree-like version number is added to the updated database. Further, the DBMS 2 is provided with means for detecting and notifying a discrepancy between version numbers, means for integrating any two databases, means for notifying the update status / version number of the current database, and the like. Help with tree integration.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database management system, and more particularly to a database management system which can introduce the concept of version number management into a database and manage the database with the version number.

[0002]

2. Description of the Related Art As a database management system (hereinafter referred to as DBMS) used in a CAD system or the like, usually, there are many systems realized by using the following two technologies. (1) The relational database is adopted because the format of the data recorded in the database and the format of the data used by the application can be defined independently. In addition, in a complicated case, the design database is often composed of a plurality of databases.

FIG. 18 is a diagram for explaining a method of defining a data format in the above-mentioned relational database. In a relational database or the like, a data format to be recorded in the database is defined by a schema. As shown, the schema allows
The name is defined as "character", item 1 and item 2 are defined as "numerical value", ..., Item N is defined as "character". Then, correspondingly, letters and numbers are recorded in each item of the database.

On the other hand, in the application, the format of data used for editing is defined by the schema,
For example, similar to the schema of the database, as shown in the figure, the name is defined as "character", the item 1 is defined as "numerical value", and the item N is defined as "character". (2) The following method is used to maintain the consistency of the database. When referring to the database, specify the data name and display the data. On the other hand, the DBMS notifies the corresponding data. At that time, management information such as data name and creation date is also attached.

FIG. 19 (a) is a diagram showing the above-mentioned processing at the time of referring to the database. As shown in the figure, when the application makes a query to the database, "I want database A", the DBMS stores the data A The "creation date XX" and its "contents YY" are notified. The application edits the referenced data and registers it in the database. At this time, the registration request is made by giving the corrected contents to the data notified at the time of reference.

[0006] In the DBMS, the creation date of the data recorded in the database is collated, the presence or absence of the update after the reference is confirmed, and the registration is performed only when there is no update. If it has already been updated, you will have to start again from the reference. FIG. 19B is a diagram showing the above-described processing at the time of registration of data. As shown in FIG. 19, the application requests the database to register with “data A, creation date XX, contents ZZ”. Then, the DBMS confirms the update as described above and notifies the application of the processing result of "registration completed" or "registration failed".

[0007]

The conventional DBMS described above has the following problems because the management system shown in FIG. 19 is used. When multiple users update a single database, only the updated data of one user can be registered. Since the update history is not a management target, it is not possible to deal with corrections that go back in the past.

The conventional DBMS has the above-mentioned problems, and it has not been possible to sufficiently deal with the CAD system or the like which requires the following conditions. -Multiple users share and create / update the database. -It is necessary to save the update history and restore the existing data even if a failure occurs during the update.

The present invention has been made in consideration of the above-mentioned problems of the prior art, and the first object of the present invention is to record all editing operations performed by a plurality of users.
Another object of the present invention is to provide a database management system capable of integrating editing work performed by a plurality of users. A second object of the present invention is to provide a database management system in which the original data is not lost even if a failure occurs during updating, and the output operation of the database can be minimized. .

[0010]

FIG. 1 is a diagram illustrating the principle of the present invention. In the figure, 1 is an application for making inquiries, registration requests, etc. with respect to the database, 2 is a database management system (DBMS), and the DBMS 2 has means for managing the version number of the database and between the version numbers of the database. A means for detecting a discrepancy and notifying the application 1, a means for integrating the version numbers of the database according to an instruction from the application side, a means for notifying the application 1 of the update status / version number of the database, a user name during database updating Is provided for recording and notifying.

Reference numeral 3 is a database, and database 3
The version number of is registered in multiple indexes. Also, the version number has a tree structure as shown in the figure, and the version number is the above DB.
It can be integrated by the integration means of MS. In order to solve the above problems, the invention of claim 1 of the present invention has, as shown in FIG. 1, a multiple index for registering a version number having a tree structure, and when the database is updated, the updated database is used. A means for adding a version number of a tree structure to manage a plurality of databases according to the version number, a means for comparing databases of different version numbers, a means for detecting a mismatched portion between the version numbers and notifying the same, and an arbitrary two or more The database management system is provided with means for integrating the version numbers of the database.

According to a second aspect of the present invention, in the first aspect of the invention, when a database is inquired, a means for notifying the update status of the database and the version number information constituting the database is provided. Is. According to a third aspect of the present invention, in the first or second aspect of the invention, means for recording and notifying the user name of the database being updated is provided.

[0013]

In the present invention, the following means are added to the conventional database management system. (1) The concept of version number management is introduced, and means for managing the database by version number is provided.

When updating the database, a tree-like version number is added to the version number database at the time of reference as a database created based on the database.
For example, in the database created from the [1.0] version as shown in FIG. 1, the first registered one is described as [1.1], and the one created thereafter is [1.0.1]. ],
It is written as [1.0.2], .... Then, in order to manage the version number of the data on the database, a multiple index is provided as shown in FIG. 1 and the version number is registered.

When the application 1 makes an inquiry to the database when referring to the database, the DBMS 2 notifies the "version number" and the "content" of the inquired database. When the data referenced by the application 1 is edited and registered in the database 3, the application 1 requests the registration with the database name, the version number and the content notified at the time of reference. Upon receiving a registration request, the DBMS 2 newly secures a data area, adds a new version number, performs registration processing of the data, and notifies the processing result.

As described above, when the data is updated, a new data area is secured and registered on the index of the new version, so that the data before and after the updating can be saved in the database. It is possible to record all editing operations performed by a plurality of users. In addition, existing data will not be lost even if a failure occurs during updating.
Since only the updated data needs to be processed, the output operation to the database can be minimized. (2) The following means are provided to support the integration of version number trees in a version number controlled database.

Although individual update data is not wasted by managing the version number, there are cases where the database is divided into a plurality of version numbers and it is difficult to know which version number is the latest version. Therefore, in the present invention, the DBMS 2 is provided with the following means. Means for detecting and notifying inconsistency between version numbers Compare databases with different version numbers and notify each data of coincidence, inconsistency, addition, deletion, etc. This makes it possible to determine which database is valid and the like, and it is possible to support the merging of the database version numbers. Means for integrating any two databases When the database to be finally adopted is determined, the version numbers [1.1] and [1.0.1] are integrated as shown in FIG. 1.2]. A means for notifying the current update status / version number of the database Notify the update status of the database and the version number information that constitutes it. In addition, management information such as update time and updated user name that is attached to the version number is also recorded, and is used when determining which version database the user will access, or referenced by the user when updating. To the database
Used to check if other users are updating. At the same time, the means for notifying the name of the user who is updating is necessary because it is necessary to communicate for the purpose of making adjustments between users who are editing the database, so record the updating user on the DBMS side, Be able to respond to inquiries.

As described above, by providing the DBMS 2 with means for supporting the integration of the databases, the editing work performed by a plurality of users can be easily integrated, and the databases can be efficiently managed.

[0019]

FIG. 2 is a diagram showing the configuration of a database management mechanism according to an embodiment of the present invention. In the figure, 11 is an application, and the application 11 is provided with an extended part 11a for managing the version number in addition to the conventional database access part 11b.

Reference numeral 12 denotes a DBMS. In addition to the conventional DBMS, the DBMS 12 is provided with an extended portion 12a for managing the version number and an access management unit 12b for performing access management. 13 is a database, 14 is created for each database, and the access management unit 12a of the DBMS 12
Is an access control list used by the access control list 14
The user name, the purpose, the reference version number, and the update version number are recorded in the field.

Next, the database management in the embodiment of the present invention will be described. A. When updating the version number database, the version number is added to the version number database at the time of reference as a database created based on that database. For example, in the database created from the [1.0] version as shown in FIG. 3, the first registered one is described as [1.1], and the ones created thereafter are described as [1.0.1]. ], [1.0.
2], ...

That is, only when the database is first updated, the direct version number (the number of digits is not changed, for example,
[1.0] → [1.1], etc., and other than that, it is collateral (the original version number with a single-digit version number added, for example,
[1.0] → [1.0.1], etc.). However, [1.
There is no priority between 1] and [1.0.1], and the relationship is that only the same version number ([1.0] in the figure) is a parent.

Note that FIG. 3 shows an example of data notified from the DBMS to the application at the time of notifying the update status, etc., which will be described later. As shown in FIG. The version update date and time, the updater, and the name of the person who is currently performing the update work are recorded in the DBMS and notified to the application. With the introduction of the above version number, database access becomes as shown in FIG.

That is, when referring to the database, when the application inquires the database that "I want the database A", the DBMS notifies the "version number XX" of the database A and the "contents YY". When editing the data referenced by the application and registering it in the database, the application is database name A.
The request for registration is made with the "version number XX" and "contents ZZ" notified at the time of reference.

In the DBMS, a new "version number XY" is added to register the data, and the database name A and the "version number XY" and "contents ZZ" are added to notify the processing result. Further, when it is necessary to handle a plurality of databases consisting of a plurality of independent elements, the above system is expanded, and as shown in FIG. 5, the element for managing the version number of each element is treated as a database. Record the version number of each component and manage the whole. In FIG. 5, [1.0], [1.1] ... in the “version number” column (left column)
[1.7] indicates the version number of the entire database, and "AA"
"1.0" in the "A", "AAB", ..., "ZZZ" column,
[1.1], ..., [1.1] indicate the version number of each component.

FIG. 6 is a diagram showing a method of managing the version number of a database in this embodiment. In this embodiment, as shown in FIG. An index that covers the data belonging to the version number is stored for each version number. For example, FIG.
, The data AAA, AAB. When the version number of ZZZ is [1.0], the index indicating the version number [1.0] points to all data.

Here, it is assumed that the database of [1.0] is referenced, the database is edited and the result is registered. When the application edits the data by referring to each of the above databases and registers the data, the DBMS 12 detects the updated data and secures a new data area,
Register on the new version index.

As a result, for example, as shown in FIG. 6B, the data before the update is recorded in the database together with the data before the update, and the index indicating the version number [1.1] is generated. It comes to point to the updated data. Next, a database update procedure in this embodiment will be described with reference to FIGS. (1) FIG. 7 shows the initial state.
Nothing is registered in 4.

In the state shown in FIG. 7, the user A uses the DBMS 12 for updating the database as shown in FIG.
Request access to. On the DBMS 12 side, it is confirmed that there is a database of the corresponding version number, and as shown in the figure, the user (user A), purpose (update), reference version number ([1.1] ) Add records and issue permissions. (2) In the application, the DBMS is queried for necessary data as shown in FIG. 9 to prepare for edit processing. (3) The update data generated as a result of processing by the application is recorded in the extended portion 11a for version number management introduced for version number management, as shown in FIG. Accumulated. (4) When editing by the application is completed, registration in the database 13 is performed as shown in FIG.

That is, first, the version number when registering in the database 13 is acquired. Note that if another application makes a registration request before the version number at the time of registration is determined by this process, separate updates may be requested for the same version number, so the exclusive control process in the DBMS Needs to be done. When the version number at the time of registration is confirmed, the application is notified of the confirmed version number (in this case, the version number [1.1.1]). At the time of subsequent registration processing, the update data with the specified version number will be notified to the database. (5) As shown in FIG. 12, the data updated by the application has only the updated data registered as update data in the database according to the update presence / absence managed by the extension part 11a for managing the version number. You will be notified with the version number. (6) When all the update data have been notified, as shown in FIG. 13, the update completion is instructed and the process of updating the version number management data on the side of the DBMS 12 is started. That is, DBMD
On the 12 side, the version number management data is updated, the data is deleted from the access management book 14, and the processing ends. Finally, when the application 11 is notified of the registration completion code, the database is officially updated.

In the above embodiment, as described in (3), the presence or absence of the update is managed by the extended portion 11a for managing the version number on the application 11 side. If it is difficult to record the presence / absence, this can be managed on the database side. FIG. 14 is a diagram showing an embodiment in which the presence or absence of updates is managed on the database side as described above. As shown in FIG. 14, in this embodiment, the result of processing by the application is stored in the DBMS 12. It will be notified and the database will record whether or not it has been updated. Then, the DBMS 12 collates the updated data with the data on the database and manages the presence or absence of the update.

FIG. 15 is a flowchart showing the above processing. As shown in FIG. 15, when the application issues an access request in step S1, the DBMS adds data to the access management list and issues access permission.
In step S2, the application makes a data inquiry to the DBMS, and the DBMS notifies the data.

In step S3, the application updates the data, and in step S4, the DBM
A registration request is made to S and the updated version number is acquired.
In step S5, the application notifies the DBMS of the updated data for registration. Then, in step S6, the database registers the update data, notifies the application side of the completion code, and the registration process is completed. B. Support for version number integration.

By managing the version number, individual update data is not wasted, but when the database is branched into a plurality of version numbers, which version number is the latest version cannot be known. This situation is undesirable and will eventually need to be integrated into one of those versions. For example, as shown in FIG. 16, [1.1], [1.0.1],
When databases of three versions called [1.0] are created, the contents of [1.1] and [1.0.1] among them are examined, and from [1.1] to [1.2] ]] Database is created, and [1.0.1] is added to the database of [1.2].
Work to absorb the contents of.

In order to support this work, in the present embodiment, the following functions are prepared so that the results of the update work of individual databases can be systematically reflected in the databases. (a) A function to notify the current update status of the database. In the format shown in FIG. 3, the application is notified of the update status of the database and the version number information constituting the update status.

In order to contribute to the next use, the management information such as the update date and time, the updated user name, etc. attached to the version number is also recorded. It is used to determine which version of database the user will access. It is used to check whether another user is updating the database referenced by the user when updating. (b) A function to notify the difference between the databases of arbitrary two versions.

As shown in FIG. 17, for example, the version number [1.
0] and [1.1] databases are compared, and notification of coincidence, non-coincidence, addition, deletion, etc. is given for each individual data. This is used when the following work is performed assuming merger. Determine which data is valid. Evaluate the impact of rebuilding the database based on the merged databases. For example, the influence of the record replaced with the specified version number of data is reflected in the database. (c) A function to integrate any two databases.

As described with reference to FIG. 16, this is a function of determining a database to be finally adopted and setting the database as the latest. Databases that have not been adopted will also coexist as past histories. When integrating databases that have been branched, integrate the mismatched parts by using the function of (b) above and match the databases. Next, when the integration is declared, the version number update history is integrated as shown in FIG.

In this integration, it is necessary to integrate the parent version number of itself (for example, the version number [1.0.1] is [1.
0]) is prohibited. (d) A function to notify the existence of users who are updating at the same time. Since it is necessary to communicate between users who are editing the database for the purpose of making adjustments, etc., the user updating is recorded on the DBMS side so that the inquiry can be answered. That is, since the user name or the like being updated is registered in the access management book 14 described above, when there is the above inquiry, the user making the update is notified by referring to the access management book. be able to.

[0040]

As described above, the following effects can be obtained in the present invention. In the invention of claim 1, the database management system is provided with means for managing a plurality of databases according to version numbers, means for detecting and notifying a mismatch between version numbers, and version numbers of arbitrary two or more databases. Since the integrating means is provided, it is possible to record all the editing work performed by a plurality of users and easily integrate the editing work performed by a plurality of users. Further, since only the updated data needs to be processed, the output operation to the database can be minimized.

Therefore, it is possible for a plurality of users to share and efficiently create / update the database, and it is also possible to retroactively make corrections. In particular, since a history is taken for each data and the changed amount is added, existing data will not be lost even if a failure occurs during updating. According to the second aspect of the present invention, when the database is inquired, the means for notifying the update status of the database and the version number constituting the database is provided. Therefore, which database should the user access? It can be easily judged. Further, it is possible to confirm whether or not another user is updating the database referred to by the user when updating. According to the third aspect of the present invention, since the means for recording and notifying the user name of the database being updated is provided, the users who are editing the database can make communication for adjustment.

[Brief description of drawings]

FIG. 1 is a principle diagram of the present invention.

FIG. 2 is a diagram showing a configuration of a database management mechanism according to the embodiment of this invention.

FIG. 3 is a diagram showing a tree structure of version numbers in the embodiment of the present invention.

FIG. 4 is a diagram illustrating access to a database according to the embodiment of this invention.

FIG. 5 is a diagram showing an extension example of the system of the embodiment of the present invention.

FIG. 6 is a diagram showing a database version number management method according to an embodiment of the present invention.

FIG. 7 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 8 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 9 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 10 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 11 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 12 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 13 is a diagram illustrating a database update procedure according to the embodiment of this invention.

FIG. 14 is a diagram showing an example in which the database side manages the presence or absence of updates.

FIG. 15 is a flowchart showing a database update procedure in the above embodiment.

FIG. 16 is a diagram illustrating version number integration in the embodiment of the present invention.

FIG. 17 is a diagram illustrating detection of a database difference according to the embodiment of this invention.

FIG. 18 is a diagram showing a conventional data management system.

FIG. 19 is a diagram illustrating conventional update / registration of a database.

[Explanation of symbols]

 1, 11 application 2, 12 database management system (DBMS) 3, 13 database 11b database access part 11a extended part for managing version number 12a extended part for managing version number 12b access control part for performing access management 14 Access control book

Claims (3)

[Claims] 1. When a database is updated with a multiple index for registering a version number having a tree structure,
Add the version number of the tree structure to the updated database,
A means for managing multiple databases according to version numbers, a means for comparing databases with different version numbers, a method for detecting and notifying a mismatch between version numbers, and a means for integrating the version numbers of any two or more databases A database management system characterized by having and. 2. The database management system according to claim 1, further comprising means for notifying the update status of the database and the version number constituting the update status when the database is inquired. 3. The database management system according to claim 1, further comprising means for recording and notifying a user name of the user who is updating the database.