JPH0293744A - Data base control system - Google Patents

Abstract

PURPOSE:To reduce the burden of a user (an information manager, an information user) and to attain information operation, which is adapted for the information control of a real world, by imposing the burden to control the condition of information on a data base control system side. CONSTITUTION:An area 70 is provided to show the transition of a requestable condition to the information in each information to be stored to a data base 20 (each table to store the information). The information of an unapproved condition 71 go to be an approved condition 72 by approval operation and the information of the condition 72 go to an open condition by open operation. Then, the information of the condition 71 or 72 go to a sealed condition 73 by seal operation. Accordingly, a user request to be inputted through a request control part 100 can be retrieved when the information of a retrieval subject are in the open condition through an information operating function control part 200, etc., or when a retrieval right is given to the information of the condition 71 and 72. In the case of updating request, when the subject information are the information of the condition 71, to which a updating right is given, the request can be updated. Thus, the burden of the user is reduced and the information operation to be adapted for the information control of the real world can be executed.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a database management system, and particularly to a database management system that provides a user interface suitable for managing document information.

[Conventional technology]

In recent years, systems for managing documents and drawings have been constructed as application systems that utilize databases and database management systems.

In the real world, the information managed by such systems, that is, documents and drawings, become official documents after the created information is examined and approved.Normally, once the information becomes an official document, it cannot be changed. Also, when sharing official documents, keep them in a shared file or cabinet so that everyone can access them. On the other hand, documents that you do not want anyone to see, such as confidential documents, should be stored in a safe or locked cabinet so that no one can access them.

On the other hand, in conventional database systems, the state of information as described above is not managed, and the operations that users can perform can be limited by the information usage authority granted by the information manager to the information user. Met. Regarding this, see, for example, Kim Seok, database specialist committee member of the Japan Electronics Industry Promotion Association: "Survey on database systems - Investigation on database security functions -" No. 167-172.
(59-C-480, published March 1982).

Therefore, in order to realize the movement of information that corresponds to the real world on a computer system as described above, conventionally, the user has to create a user program that manages the state of the information as described above, or We had no choice but to deal with the problem by operating the database.

When a user deals with database operations, a view function is a useful database operation function provided by a database management system.

The view function defines how the database is viewed when a user or an application program uses the database, out of the information in the database. In other words, a part (divided vertically or horizontally) of a logical storage unit (one table in the case of a relational database management system) or a combination of multiple tables can be defined as a view. The user can manage the state of information by adding flag information for state management to the table and defining views according to each state.

[Problem to be solved by the invention]

When managing information having the above-mentioned states using an existing database management system, the burden on the user was large because the management was conventionally handled by user programs or operations as described above. In addition, authority is managed in units of files that store information, and if you have authority, you are allowed to update all information in that file, so it is not possible to manage the status of each individual information unit.

Further, in the method using the view function, it is necessary to define a view for each state and manage the authority of the view, which places a heavy burden on the information administrator who manages these. Also,
When a user uses information whose status has changed, he or she must change the operation target (view) and issue an operation request, which places a heavy burden on the user.

The present invention has been made in view of the above-mentioned circumstances, and its purpose is to solve the above-mentioned problems in the conventional technology, and to offload the management of information status to the database management system. The purpose of this invention is to provide a database management method that reduces the burden on information managers and information users (information managers and information users), and enables information operations that are consistent with real-world information management.

[Means to solve the problem]

The above object of the present invention is to provide, in a database management method in a database management system, an area for storing status information indicating possible operations on the information for each piece of information stored in the database, and to store the status information of the stored information in the storage area. This is achieved by a database management method characterized by setting information and restricting operations on the corresponding information based on the status information.

[Effect]

As described above, in the database management method according to the present invention, management of the state of information stored in the database is realized as a function provided by the database management system.

A user first stores information in a database. Information stored in the database is in an unapproved state at the time of storage. Information in an unapproved state can be searched and updated only by a user who has been given the corresponding operation authority by the information manager. Furthermore, when an administrator of the information performs an approval operation, information in an unapproved state becomes an approved state in which only a user to whom the information manager has given search authority can search and no user can update the information.

When the information in the approved state is made public by the administrator of the information, the information becomes public so that anyone can refer to it but cannot update it. Information that is public can be accessed by users who are registered in the system, even if they are not given search authority.

Anyone can search. The information in the public state returns to the original approved state by a non-public operation. To place unapproved or approved information in a sealed state where no one can search or update it, you can request a sealing operation. On the other hand, by releasing the sealed state,
To return to the original unapproved/approved state, a seal release operation is required.

When a user requests a search, the user can search if the information to be searched is public, or unapproved or approved information for which search authority has been granted. When a user requests an update, the information to be updated can be updated if and only if the information is in an unapproved state for which update authority has been given.

Requests for approval, disclosure/disclosure, sealing/unsealing.

This is done by the information manager. Approval requests are made only for information that is in an unapproved state. Publication requests are made only for information in an approved state. Non-disclosure requests apply only to information that is public. Sealing requests are only applicable to information in approved or unapproved status. The unsealing request applies only to information on the sealed state.

Information managers can perform all information operations and status operations on the information they manage. Other users can execute the corresponding information operations by being given execution authority corresponding to each information operation by the information manager.

〔Example〕

Embodiments of the present invention will be described in detail below with reference to the drawings. In the following description, for convenience of explanation, a relational model is assumed as the data model provided by the database management system. The relational model is a data model that has a tabular structure, as shown in the example of the table definition management table 31 in FIG.
Columns in a table correspond to fields in a conventional file, and rows correspond to records. In the embodiment shown below, the description will be made assuming that the Lou code corresponds to one piece of information.

FIG. 2 is a diagram showing the minimum hardware configuration for implementing the present invention. In the figure, 40 is a computer on which the database management system that implements the present invention operates, 50 is a terminal (keyboard and display) that interfaces with the user, and 60 is a secondary storage device that stores the database and data dictionary. Generally, a plurality of terminals 50 and secondary storage devices 60 are provided.

First, as a first embodiment, an example will be shown in which the state is managed in table units. FIG. 5 shows a situation in which a status information column 134 is added to the table definition information management table 31 held in the data dictionary 30, and the contents of this status information column 34 can be changed. This allows the state of information in the table to be changed.

In the example of FIG. 5, one record (row) of table definition information held in the table definition information management table 31 becomes definition information of one table. The table definition information includes status code information 34 in addition to the owner name 32 and table name 33. The content of the status code information 34 may be any code information that can identify the following five statuses.

- Unapproved state - Approved state - Public state - Unapproved state information is sealed - Approved state information is sealed In Figure 5, the table name (33) employee of the owner (32) satoh is Approval status (code 20
0). The operation will be explained below.
FIG. 1 is a block diagram of a database system to which the present invention is applied. This system is a database management system 10. It consists of a database 20° and a data dictionary 30. This database management system 10 is software that runs on the computer 40 mentioned above.

As shown in Figure 1, this database management system 10 includes an information operation function management section 200 under a request control section lOO.
．． State operation function management section 300. Information definition function management department 40
0. Information manipulation processing execution unit 500. State manipulation processing execution unit 6
00 and a data dictionary management section 700.

Furthermore, a rectangular box 70 below the database 20 indicates a state transition in which a request can be made to the information stored in the database 20 (here, a table storing the information). The information in the unapproved state 71 changes to the approved state 72 by an approval operation. Information in the approved state 72 changes to a public state 74 by a public operation. Public status information 74
returns to the approval state 72 by private operation. Approval status 7
2 or unapproved state 71 becomes sealed state 73 by sealing operation. The information of the sealed state 73 is 1, and the state returns to the state before sealing by the unsealing operation. Note that information that has been changed to the approved state 72 cannot be returned to the unapproved state 71.

Additionally, the information in the data dictionary 30 is typically accessible to users for easy database management. The user can also grasp the state of information by referring to the table definition information management table 31 in the data dictionary 30, as in the past.

A request from a user to the database management system 10 is first received by the request control unit 100.

The processing flow of the request control unit 100 is shown in FIG.

The request control unit 100 receives a request from a user and analyzes the content of the request (step 101). The content of the request is checked (step 102), and if it is an information manipulation request, the information manipulation function management section 200 described above is called (step 103). If the request is for state manipulation, the state manipulation function management section 300 is called (step 104). If the request is related to information definition or authority definition, the information definition function management section 400 is called (step 105). When the processing of each function management section is completed, the execution result is returned to the user (step 10).
6), Finish.

The processing flow of the information operation function management section 200 is described in the eleventh section.
As shown in the figure. After analyzing the content of the requested operation (step 201), the information operation function management section 200 calls the data dictionary management section 700 to retrieve definition information and authority information of the requested object, while checking the existence of the processing object (step 201). Step 202), Check user authority (Step 20)
3) and a processing validity check (step 204). That is, when the processing request is a search, the search is allowed if the table to be searched is in the public state, or if the table is in the approved or unapproved state and the search authority is granted.

If the processing request is an update, the update is allowed if the table to be updated is in an unapproved state and update authority has been granted. If there are no errors in these checks,
Step 205) Calling the information manipulation processing execution unit 500
, requests execution of the requested process. Once the processing is complete,
The result is returned to the caller (step 206).

The information manipulation function management section 200 sends parameter information 800 as shown in FIG. 3 to the information manipulation processing execution section 500.
Hand over to. The operation target 801 of the parameter information 800 is
This is the identifier of the table to be operated on. The operation mode 802 is code information indicating the content of the operation, that is, searching for, adding, changing, or deleting information. The operation condition 803 is a condition of information (record) to be operated. When adding or changing the input/output area address 804,
Input/output area 805 that stores values to be set in records
This is the address. In the case of search, the above input/output area 805
is an area that receives search results, and the input/output area address 804 is that address.

The processing flow of the information manipulation processing execution unit 500 is shown in FIG. The information manipulation processing execution unit 500 receives parameter information 8
Processing is distributed based on the operation mode 802 of 00 (step 501). If the operation mode is addition, a record with the value set in the input/output area 805 is generated (step 508) and stored in the table specified by the operation target 801 (step 509). In other cases, set the operation conditions 803 when retrieving the record to be operated from the table specified as the operation target 801 (step 502), and skip the processes in steps 504 to 507 until the record search is completed. return.

That is, after searching for a record (step 503), it is checked whether the search has been completed (step 504), and if it has not been completed, the operation mode is checked in step 505. In the case of information search, the searched records are set in the input/output area 805 in order to be returned to the user (step 507). Further, in the case of modification, the searched record is changed to the value specified in the input/output area 805 and returned to the table, and in the case of deletion, the record to be searched is deleted (step 506).

The processing flow of the state manipulation function management unit 300 is described in the 12th
As shown in the figure. After the state manipulation function management unit 300 analyzes the content of the requested manipulation (step 301).

While calling the data dictionary management unit 700 and retrieving the definition information and authority information of the request target, the existence of the processing target is checked (step 302), the user's authority is checked (step 303), and the validity of the process is checked (step 3).
04). That is, when the processing request is a public operation request, the table targeted for the operation must be an unsealed table in an approved state. If the processing request is a private operation request, the table that is the target of the operation must be a public table.

Also.

In the case of an approval request, the table to be updated must be in an unapproved state. If there are no errors in these checks, the state manipulation processing execution unit 600 is called (step 305), requesting execution of the requested processing. When the process is completed, the result is returned to the caller (Step 3)
06).

The state manipulation function management section 300 sends parameter information 810 as shown in FIG. 4 to the state manipulation processing execution section 600.
Hand over to. The operation target 811 of the parameter information 810 is
This is the identifier of the table to be operated on. The operation mode 812 indicates the content of the operation, that is, approval, public/private,
This is code information indicating either sealing/unsealing or status information search.

The processing flow of the state manipulation processing execution unit 600 is described in the fourteenth section.
As shown in the figure. The state manipulation processing execution unit 600 executes the requested processing based on the parameter information 810. At first,
The contents of the request are checked (step 601). If the request content is a state information search request, parameters such as search targets are set (step 604), and a state information search request is issued to the data dictionary management section 700 in step 605. In addition, if the request content is a state information change request, the change target,
Step 602) to set parameters such as changes, etc.
In step 603, a status information change request is issued to the data dictionary management unit 700.

The aforementioned information definition function management section 400 calls the aforementioned data dictionary management section 700 and checks the validity of the processing while retrieving the definition information and authority information of the requested object, and if there is no error, the information is sent to the data dictionary management section 700. , requests execution of the requested process. No particular processing flow is shown.

The data dictionary management section 700 includes the information operation function management section 2.
00, state manipulation function management section 300. It is called by the information definition function management unit 400 and executes the requested process.

The processing flow of the data dictionary management section 700 is shown in FIG. First, check the request content (step 701).
). If the request content is a search request, information in the specified data dictionary is searched and returned (step 702). In the case of addition, the specified record is added to the specified data dictionary table (step 703). In the case of modification, the designated record in the designated data dictionary table is modified (step 704). In the case of deletion, the specified record is deleted from the specified data dictionary table (step 705).

The embodiments have been described above in which the state of information is managed on a table-by-table basis. With this method, it is only necessary to manage the information status on a table-by-table basis, so implementation and status management are easy.

Next, as a second embodiment, an embodiment suitable for users who wish to manage status more precisely for each piece of information will be described.

In this embodiment, status information is held in records in order to manage the status on a record-by-record basis. FIG. 6 shows a method for maintaining the information state. Figure 6 shows
This shows an example of a method for holding status information in a record 820, in which a status code 822 indicating the status is placed between the header part 821 of the record and the record body 823.

The above status code 822 includes unapproved and approved.

All you have to do is set a code to classify the status as open or sealed. Since the sealed state can also be used as an unapproved or approved state, the sealed state is divided into an unapproved sealed state and an approved sealed state. Alternatively, it is also possible to use a method in which the status code 822 is treated as a bit string, each bit is associated with a respective status, and the status is determined by turning on/off the bits. In either case, the change in status is indicated by status code 822.
This is done by changing the value of .

The operation will be explained below.

The functional configuration of the database management system 10 is the same as that of the first embodiment shown above, and is shown in FIG. The processing of the request control unit 100 is also similar to that of the first embodiment. What is different from the first embodiment shown above is the information operation function management section 200. Information manipulation processing execution unit 500. State operation function management section 300. This is the flow of processing by the state manipulation processing execution unit 600. The flow of processing in each section is shown below.

FIG. 16 shows a processing flow of the information operation function management section 200 in this embodiment. The difference from the first embodiment shown in FIG. 11 is the validity check part (
This is the point where step 204) changes to generation of parameter information (step 208). Also in this embodiment, the information manipulation function management section 200 delivers parameter information 800 as shown in FIG. 3 to the information manipulation processing execution section 500. However, the operation mode 802 includes the contents of the operation, that is, searching only for information in a public state, searching for information in a state other than a sealed state, and adding.

Code information indicating either modification or deletion.

Furthermore, a search request from a user who is not given the search #i limit results in a search for only public information. A search request by a user with search authority is a search for information in a state other than the sealed state. Requests for additions, changes, and deletions will be carried over as is. Other parameters are the same as in the first embodiment described above.

The processing flow of the information manipulation processing execution unit 500 is shown in FIG. The information manipulation processing execution unit 500 executes the above parameter 8.
Based on 00, the requested process is executed.

The processing in the case of addition is similar to the first embodiment described above, in which a record with the value set in the input/output area 805 is generated and stored as an unapproved state in the table specified by the operation target 801. (Step 501゜508.509)
. In other cases, a record that satisfies the operation condition 803 is retrieved from the table specified by the operation target 801 (5
02,503). The difference from the first embodiment described above is the processing after the record search, which is divided as follows depending on the operation mode.

(1) In the case of searching for only public information, check whether the searched record is public (step 511);
Only records in the open state are set in the input/output area 805 in step 507.

(2) When searching for information in a state other than the sealed state, check whether the retrieved record is in the sealed state or not.Step 51
2) Only records other than those in the sealed state are processed in step 507.
Then, set it in the input/output area 805.

(3) In the case of modification or deletion, check whether the retrieved record is not in a sealed state and is in an unapproved state (Step 510)
), if so, in step 506, the requested modification or deletion process is performed.

Next, FIG. 17 shows a processing flow of the state manipulation function management section 300 described above. The difference from the first embodiment described above is that
The validity check process (step 3o4) becomes the parameter information generation process (step 308).

Since status information is held on a record-by-record basis, it is not possible to determine the status or check the validity of status operations until a record is searched. Therefore, here:
Parameter information 810 as shown in FIG. 4 is generated and delivered to the state manipulation processing execution unit 600. The contents of the parameter information are the same as in the first embodiment.

The processing flow of the state manipulation processing execution unit 600 is shown in FIG. Since the status is managed on a record-by-record basis, the processing is different from the first embodiment. First, the specified operation target (
(steps 606 and 607). If the search is not completed (step 60g), the operation mode is checked (step 609), and the following processing is performed.

(1) In the case of a public operation, check the status of the record (step 610), and if the record is in an approved status that is not sealed, set the status information of the record to the public status (step 611).

(2) If the operation is private, check the status of the record (step 612); if the record is public, release the public status and return the record status information to the approved status (
step 613).

(3) In the case of a sealing operation, check the status of the record (step 614), and if the record is neither published nor sealed, that is, the record is in an unsealed, unapproved or approved status, the status information of the record is checked. Set to sealed state (step 61
5).

(4) In the case of unsealing operation, check the status of the record (step 616), and if the record is in a sealed status, the sealed status is canceled and set to the unsealed status (step 617).

(5) In case of approval operation, check the status of the record (step 618), and if the record is unsealed and unapproved, set the status information of the record to approved status (step 619).

The above processing (steps 607 to 619) is repeated until the record search is completed. Information definition function management department 40
0. The processing flow of the data dictionary management unit 700 is the same as in the first embodiment.

In this embodiment, the state of information is managed on a record-by-record basis. Therefore, as in the case of the first embodiment, it is not possible to grasp the state of the record just by referring to the data dictionary. To solve this problem, record status information should be returned together with the record search.

Next, a third embodiment that is a further development of the above-described embodiment will be shown. In this embodiment, as shown in FIG. 7, a method is adopted in which the physical storage areas in the database 20 are divided according to each state. In FIG. 7, a storage area 21 for information in an unapproved state and a storage area 22 for information in an approved state are shown.
．． Storage area 2 for information with unapproved information sealed
3. Storage area 2 for information with sealed approval status information
4. It is divided into five storage areas 25 for information in a public state.

For state management, the management information of each divided storage area is held in the data dictionary 30, and the information manipulation function management section 200 and the state manipulation function management section 300 refer to this information and perform information and state operations. The information manipulation processing execution unit 500 and the state manipulation processing execution unit 600 are instructed. The state of information is changed by moving the information between storage areas.

Next, a fourth example will be shown. In this embodiment, the state information held in each record 820 in the second embodiment (see FIG. 6) is held in each entry of the primary key index. be. The primary key index is an index created based on key data (primary key) for uniquely identifying the record 820.

FIG. 20 shows an example in which the primary key index has state information. The structure of the index is similar to a general index. The difference is that the entry section for each record in the leaf node 852 in the primary key index 850 has a state information storage field 853 that holds a state code indicating the state. The above-mentioned state operation is performed by changing the state code in this state information storage field 853. The processing method of the database management system IO for information manipulation and state manipulation requests is based on the above-mentioned second method.
This is the same as in the embodiment. The difference is that the information search is performed using the primary key index 850, and the state is determined during the index search.

The advantage of this embodiment is that it is possible to reduce the number of I10 times in the data section during condition-specified information search processing.

A group of pointers to records that satisfy the condition obtained from the index created in the field specified by the condition, and a group of pointers to records having the state targeted for the search obtained from the primary key index 850. By merging the pointers and inks between them, a group of pointers to the records to be searched can be obtained. After narrowing down the search at the index level, the actual record 820 group is read.

In the fourth embodiment described above, the primary key index,
Although the method using 950 has been described, next, a fifth embodiment will be described in which an index based on the state information itself is used.

An example of the configuration of the status index 860 used in this embodiment is as follows:
The state index 860 shown in FIG. 21 has a two-level hierarchy consisting of only a root node 861 and a leaf node 862. The root node 861 includes a code indicating each state, and
Consists of pointers to leaf nodes 862 in each state. Leaf nodes 862 become a list of pointers to records for each state. Changes in state are achieved by moving pointers between leaf nodes 862. Note that root node 8
By associating the position of the pointer in 61 with the state, it is also possible to hold only a pointer to each state's path node 862.

According to this embodiment, it is possible to easily and quickly search for records in a specific state. Further, the merging process of pointer lists shown in the fourth embodiment described above can also be easily realized. Furthermore, this embodiment is based on the above-mentioned second. Third.
It is also possible to use the fourth embodiment together.

When managing the state of information, in the real world, information such as who did what with what information, and when, is important. Therefore, it is useful information for the user for the database management system IO to acquire history information of such state operations. The sixth embodiment described below is an embodiment in which the database management system IO manages records of state operations requested by users.

The state manipulation function management unit 300 shown in FIG. Stores recorded information.

An example of the format of recorded information is shown in FIG. In the figure, 36
37 indicates the executing user, 37 indicates the execution date and time, and 38 indicates the execution request (request target, requested state operation, requested state operation condition). It is assumed that there is one state operation record management table 35 in the system, but it is for each user.

A method of having each table separately is also conceivable. When the information operation function management unit 200 receives a search request for this table 35 from a user (information manager), it accepts the request and returns the result. Similarly, when a deletion request is received, it is assumed that the information has become unnecessary and the information is deleted. Additions or changes are not permitted.

Finally, a seventh example will be shown. This embodiment shows a document management system 900 using a database management system 10 having a state management function. The document management system 900 and database management system 10 of this embodiment operate on the computer 40 shown in FIG. Of course, in the case of a distributed system, it may be run on separate computers.

The document management system 900 manages document information using the database management system 10, accepts user requests for document information, and issues database operation requests corresponding to the user requests to the database management system 10. It realizes operational functions such as registration, modification, disposal, approval, publication/non-disclosure, and sealing/unsealing of document information.

The document management system 900 includes a processing control unit 910 that accepts requests from users and distributes processing according to the content of the requests, a registration processing unit 9209, an editing processing unit 930, and 930 that manage processing corresponding to each request from the user. Waste processing section 940. Approval processing unit 950. Public/private processing unit 96
0. It is composed of a sealing/unsealing processing section 970 and the like. Each of the processing units described above converts a request from a user into a database operation request corresponding to the user's request, and requests the database management system 10 to execute the process (see FIG. 9).

According to this embodiment, a user who constructs a document management system can directly convert operations such as approval, disclosure/disclosure, and sealing/unsealing into database operation requests, thereby facilitating development. Furthermore, since the management of the information status can be entrusted to the database management system, there is also the advantage that the troublesome management is eliminated.

〔Effect of the invention〕

As described above, according to the present invention, it is possible to realize the management of the state of information stored in a database as a function provided by a database management system, thereby reducing the burden on users (information managers and information users). This has the remarkable effect of realizing a database management system that can reduce the amount of data and perform information operations that are consistent with real-world information management.

[Brief explanation of drawings]

Figure 1 is a configuration diagram of a database system that is an embodiment of the present invention, Figure 2 is a diagram showing the minimum hardware configuration for implementing the present invention, and Figure 3 is an information operation function management unit that executes information operation processing. A diagram showing an example of parameter information to be passed to the department,
Figure 4 is a diagram showing an example of parameter information passed by the state manipulation function management unit to the state manipulation processing execution unit, Figure 5 is a diagram showing an example of a table definition management table, and Figure 6 is a diagram showing a case in which state information is provided. Figure 7 is a diagram showing an example of a record format, Figure 7 is a diagram showing an example of a method of changing the storage location depending on the state of information, and Figure 8 is a diagram showing an example of a method of changing the storage location depending on the state of information.
9 is a diagram showing an example of the format of a status operation record management table, FIG. 9 is a diagram showing an example of the functional configuration of a document management system using the database management system of the present invention, and FIG.
15 to 15 are flowcharts showing the operation of the first embodiment, FIGS. 16 to 19 are flowcharts showing the operation of the second embodiment, and FIG. 20 is a flowchart showing the operation of the second embodiment. The figure shown in FIG. 21 is a diagram showing an example of a state index. lO: database management system, 20: database, 30: data dictionary, 31: table definition information management table, 35: state operation record management table, 40: computer, 50: terminal, 60: secondary storage device, 70: state Transition, 71: Unapproved state, 72: Approved state, 73: Sealed state, 74: Public state, 100: Request control section, 200: Information manipulation function management section, 300: State manipulation function management section, 40
0: information definition function management section, 500: information manipulation processing execution section, 600: state manipulation processing execution section, 700: data dictionary management section.

Claims (1)

[Claims] 1. A database management method in a database management system, which provides an area for storing status information indicating possible operations on the information for each piece of information stored in a database, and stores the status information in the storage area. A database management method characterized by setting status information of information and restricting operations on the corresponding information based on the status information. 2. The database management system according to claim 1, wherein the state information is added to the information itself as the area for storing the state information. 3. The database management system according to claim 1, wherein the area in which the information is stored is divided by state, and the state of the information is distinguished depending on the storage location of the information. 4. The database management system according to claim 1, wherein the state information is added to an entry of an index created for the primary key of the information as the area for storing the state information. 5. The database management method according to claim 1, wherein the state information is added to management information of a logical file that stores information as the area for storing the state information. 6.Claim 1, wherein the states indicating possible operations on the information include a state in which only reference is possible, a state in which reference and update is possible, and a state in which neither reference nor update is possible.
Database management method described. 7. The states that indicate possible operations on the information include a state where all users of the system can only view it (public state), and a state where only users who are allowed to view the information can only view it. (approved state), a state in which only authorized users can perform operations on the information (unauthorized state), and a state in which all users of the system cannot view or update the information. 2. The database management system according to claim 1, further comprising an impossible state (sealed state). 8. The means for setting or changing the status information in the storage area of the status information, when creating the information, according to claim 6 or 7.
2. The database management method according to claim 1, wherein any of the states described in the above is set. 9. The means for setting or changing status information in the status information storage area is configured to:
setting the information in the unapproved state according to claim 7, and changing the information in the unapproved state to the approved state according to a user's approval operation request;
Information in the approved state is changed to public state by a user's public operation request, information in public state is changed to approved state by user's private operation request, and information in unapproved or approved state is changed by user's seal operation request. Accepts information state manipulation requests from users and changes the specified information state, such as changing the state to sealed state and changing the sealed state information to the original unapproved or approved state based on the user's unsealing operation request. The database management method according to claim 1, characterized in that: 10. A claim characterized in that a recording area is provided for the contents of the request when accepting an information status change operation request from the user, the request contents are registered in the recording area, and the request is searched and deleted according to the user's search and deletion request. The database management method described in Section 1. 11. The database management system according to claim 1, wherein the state of the information is managed by providing an index for each state that points to a group of information in that state. 12. The database management system according to claim 1, wherein the information stored in the database is a document or a drawing.